►
Description
A virtual meetup hosted by the Hyperledger India Chapter on May 18, 2022 about the Hyperledger FireFly project.
Agenda
* 20 minute FireFly intro and overview (Steve Cerveny, Founder and CEO at Kaleido)
* 20 minute panel with FireFly customers (Jason Yu, CEO at Tradego; Vinod Sharma, CTO at Ascend Bit; Sharkrit Impat, Head of Platform Engineering at Ascend Bit. Moderated by Sophia Lopez, Founder and COO at Kaleido)
* 15 minute demo (Nicko Guyer, Senior Full Stack Engineer at Kaleido)
* 5 minute Q&A
More about Hyperledger FireFly is at: https://wiki.hyperledger.org/display/labs/Firefly
B
B
Okay,
hi
everyone
very
good
morning,
good
afternoon
and
good
evening.
Some
of
you,
you
know,
may
be
experiencing
18th
of
may
and
you
know,
while
the
presenters
mostly
will
be
experiencing
17th
of
may
today,
so
it
is
going
to
be
a
you
know
very
interesting
session
and
I'm
quite
excited
to
you
know,
join
the
session.
B
C
C
Please
stay
tuned
for
that,
and
a
discussion
on
some
real
usage
of
our
firefly
and
with
then
nico
is
going
to
take
us
for
a
live
demo
of
the
features
of
version
1.0
and
we'll
have
time
at
the
end
for
for
q
and
a
so
with
that.
Let
me
lead
off
by
before
we
talk
about.
What's
new,
what's
released,
what's
part
of
the
v1
delivery,
I
want
to
step
back
and
talk
about
the
firefly
projects
and
the
problem
that
it's
trying
to
solve.
C
So,
hopefully
there's
lots
of
developers
on
on
the
call
here
today,
and
maybe
some
of
you
are
already
developing
web
three
blockchain
applications.
Maybe
some
of
you
have
been
tasked
with
trying
to
develop
your
first
one
and
the
reality.
Is
it's
a
complicated
task?
It's
a
task
that
needs
a
new
and
different
approach
to
building
an
application
to
what
you're
used
to
with
the
traditional
web
2
applications
you've
got
to
choose
a
blockchain.
C
You've
got
to
work
out
how
to
integrate
with
that
blockchain
you've
got
to
think
about
tokens
and
how
to
how
do
the
token
economics
fit
into
your
use
case?
You've
got
to
work
out
how
to
account
for
the
digital
assets
that
you're
going
we're
going
to
form
a
core
part
of
that
solution.
Think
about
keys,
think
about
what
data
can
go
on
the
chain.
C
What
days
you
can
go
off
of
the
chain,
there's
a
lot
of
plumbing
before
you
get
to
actually
building
a
really
interesting
application,
and
a
lot
of
these
are
the
very
first
challenges
you
hit.
You
open
your
code,
editor
and
you're,
presented
with
a
dizzying
array
of
complex
neutrals
and
very
hard
low-level
problems
to
solve,
and
then,
as
you
go
on
through
the
project,
you
find
that
things
just
just
get
get
larger.
You
need
to
think
about.
Well,
how
many
blockchains
am
I
integrating
with?
Is
it
one?
Is
it
multiple?
C
How
do
I
get
the
level
of
reliability
and
scale
that
I
need
for
a
production
deployment?
How
do
I
build
a
way
to
see
the
history
which
the
blockchain
itself
is
not
able
to
return
to
me
natively?
How
do
almost?
Certainly,
if
you're
here
interested
in
hyper
ledger
projects,
you
can
think
about
things
like
security
and
how
an
enterprise
solution
to
to
integrate
together
the
approach
the
firefly
project
is
there
to
provide
a
solution
to
provide
a
stack
to
provide
a
platform.
C
C
That
gives
you
a
starting
point
that
works
a
starting
point
where
you
have
a
pattern,
a
starting
point,
where
you
can
see
the
shape
that
your
application
should
be
if
it
needs
to
be
a
blockchain
application,
and
you
don't
need
to
start
with
the
public
plumbing.
You
can
start
with
the
business
logic.
You
can
apply
the
pattern
and
start
building
your
application.
C
This
is
true
for
every
single
other
type
of
application
that
you
build.
It's
true
for
all
various
types
of
web3
and
enterprise
applications
in
the
past.
Why
is
it
not
true
for
for
for
blockchain?
That's
really
the
the
mission
that
the
the
firefly
project
started
off
with
was
to
make
a
plugable
easy-to-use
development
framework
for
building
enterprise
grade
web
3
applications
that
embrace
tokens
that
are
able
to
deal
with
multiple
different
blockchain
platforms,
so
the
journey
so
far
the
the
project
actually
for
people
like
me,
actually
started
about
four
years
ago
now.
C
C
It
provides
a
gateway
for
connecting
to
smart
contracts
across
multiple
different
blockchains,
not
just
blockchains.
Within
the
hyper
ledger,
stable,
but
obviously
including
those
so
hyperledger
basu,
but
also
all
other
ethereum,
blockchains
and
hyperledger
fabric,
as
well
all
inside
of
one
api
front
door.
C
Today,
and
as
well
as
the
core
capabilities
of
the
platform,
the
version
one
suite
as
you'll
see
has
a
lot
of
features
for
developers
which
are
beyond
just
the
code.
It
has
a
cli,
it
has
a
user
experience.
It
has
a
way
to
get
yourself
running
in
just
a
few
minutes
on
your
laptop
as
you'll
see
from
niko
later
in
the
session.
C
So,
let's
just
talk
for
a
minute
about
the
the
capabilities
that
it
has
and
this
this
architecture
with
the
colored
sections
called
out
here
shows
the
features
of
firefly
and
we
call
it
a
supernode
and
really
this
evolving
term
in
the
web.
3
space
firefly
is
the
first
open
source
project
trying
to
tackle
the
problem
of
the
supernode,
and
this
means
it
is
not
itself
a
blockchain.
It
is
not
another
dlt,
it
sits
around
and
above
the
the
blockchain.
C
It
sits
as
that
middleware
tier
in
between
your
application
code
and
the
blockchains
that
you're
integrating
with
and
it
provides
apis.
It
provides
apis
that
allow
your
application
to
integrate
with
any
blockchain
smart
contracts.
It
will
generate
you
an
api
for
that
smart
contract.
It
will
give
your
application
access
to
all
of
the
events
that
are
inside,
of
that
smart
contract
and
all
blockchains
are
an
event-driven
programming
paradigm.
C
This
ability
to
not
just
be
able
to
have
smart
contracts
that
are
digital
assets.
Have
the
audit
history
of
chain
of
digital
assets
have
apis
and
wallet
management
and
the
ability
to
to
connect
to
those
digital
assets.
Move
them
see
the
history
of
them
see
the
lineage
of
those
of
those
additional
assets.
The
way
I
think
about
this
is
that
these
these
token
constructs
these
digital
assets
are
to
blockchain
what
create
retrieve,
update
and
delete
out
of
databases,
they're
the
air
and
water
of
the
system.
The
blockchain,
really
with
these.
C
Without
these
coding
constructs
the
the
blockchain
is
sort
of
incomplete.
So
why
are
there
not
apis
that
allow
you
to
address
those
directly,
so
firefly
provides
that
in
an
open
and
plugable
way.
In
order
to
do
this,
it
actually
needs
a
brain
with
a
database
to
store
the
private
data
that
you've
received
to
to
buffer
that
be
the
audit
gateway
for
that
between
your
application
and
the
blockchain.
C
So
that's
what
firefly
1.0
is
in
a
nutshell.
I'm
going
to
talk
briefly
through
some
of
the
those
capabilities
in
a
bit
more
detail
here.
We
we
look
at
the
difference
between
what
you
would
need
to
build,
with
or
without
firefly
and
existing
users
of
of
fireflies.
That's
involved
and
you'll
you'll
hear
some
of
them.
Talking
later
have
told
us
that
about
80
of
the
code
that
they
would
need
to
build
is
provided
for
them
when
you
start
with
from
firefly.
So
you
need
to
build
80
percent
less
code.
C
Now
that's
80
percent,
less
boring
plumbing
code,
which
gives
you
all
of
that
time
back
to
focus
on
what
differentiates
your
application,
the
business
logic,
the
user
experience,
the
use
case,
the
token
economics,
the
the
value
that
you
are
uniquely
providing,
rather
than
building
event
connectors
and
low-level
blockchain
connectivity
and
wallet
management
document
document
transfer.
All
of
these
low-level
capabilities
that,
on
their
own,
are
very
boring
until
you've
built
a
use
case
on
top
of
them.
C
With
the
methods
on
that
smart
contract,
so
a
generator
for
apis
for
any
smart
contract
on
the
blockchain
and
not
just
in
the
transaction
direction,
but
also
in
that
event
streaming
direct
direction.
It
has
a
built-in
event
bus
which
is
able
to
track
which
events
you've
seen
from
the
blockchain
and
which
you
haven't
it
will
transform
them
all
into
friendly,
json
payloads
and
deliver
them
to
you
with
scale
and
batching
and
an
optimized
delivery,
but
also
with
reliability.
C
This
can
be
any
blockchain
technology
that
can
plug
in
so
so
there's
a
lot
of
a
lot
of
innovation
going
on
actually
increasing
that
catalog
to
deal
with
lots
of
different
blockchains
utxo
based
blockchains.
You
know
think
bitcoin
here
could
be
a
connector
for
this,
as
well
as
something
like
fabric.
That's
the
level
of
flexibility
built
into
the
into
the
application.
C
They
often
are
connected
to
rich
on-chain
transfers
of
data
and
value
of
tokens.
But
the
business
context
is
private,
it's
sensitive,
it
needs
to
be
coordinated
off
chain
and
the
data
needs
to
flow
off
chain
and
the
interactions
with
the
core
enterprise
systems.
The
core
system,
integration,
the
triggering
of
business
processes,
the
triggering
of
sensitive.
C
As
a
message
queuing
system
that
you've
built
for
your
business
network
completely
pluggable,
and
when
we
talk
about
digital
assets
as
this
first
class
construct
on
the
api,
that
also
extends
to
the
data
model,
the
state
that's
inside
of
firefly
and
we'll
talk
a
little
bit
more
about
how
firefly
is
really
a
brain.
It
it
has
it
knowledge
of
the
state
of
the
blockchain.
It's
constantly
keeping
up
to
date
with
that
state.
So
if
you
point,
for
example,
firefly
at
an
existing
token
on
public
ethereum,
it
will
index
every
transaction.
C
With
these
token
economies
to
be
a
gateway
between
your
enterprise
and
all
this
value
that
is
out
there
or
to
allow
you
to
build
a
new
token
economy
with
rich,
tooling
and
apis
to
model
those
digital
assets,
launch
them
and
and
interact
with
them.
I
keep
on
mentioning
this
brain
term
and
it
really
is
true.
If
you
look
at
the
core
of
firefly,
what
you'll
actually
notice
is
that
a
lot
of
the
code
is
in
this
orchestration.
C
I
hope
there's
lots
of
technologies
out
out
there
that
this
this
will
resonate
with
when
you
think
about
a
technology.
That's
we're
all
familiar
with
now,
like
docker
docker
existed
for
a
period
of
time
and
on
its
own
it
was
a
very
raw
tool,
and
for
anybody
like
me
who
works
with
docker
every
day,
we
don't
just
use
docker,
we
use
an
orchestration
framework
on
top
of
it.
C
So
we
really
do
think
of
that
as
a
stateful
brain,
not
just
a
gateway
to
connect,
and
that
means
it
does
manage
lots
of
different
types
of
states.
We
talked
about
digital
assets,
data
data
that
you
have
or
haven't
transferred
to
other
parties,
data
that
you've
received
from
other
parties
on
the
business
network,
which
may
not
all
have
come
through
the
blockchain,
the
blockchain
state
itself,
those
those
blockchain
events,
the
blocks
they're
in
the
transaction
hashes
the
network
state.
C
So
that's
an
overview
of
firefly
as
a
whole
and
you're
gonna
see
some
of
the
rich
tooling
that
comes
with
it,
which
will
allow
you
to
get
going
with
this
really
quickly.
Now,
with
no
further
ado,
I
think
we're
gonna
we're
gonna,
stop
talking
about
it
and
we're
gonna
at
a
high
level
and
we're
gonna
move
to
the
panel
and
you're
going
to
hear
from
some
people.
Who've
implemented
this
directly
and
the
value
that
it's
provided
to
them,
and
then
we're
going
to
drop
down
and
you're
going
to
see
it
in
action.
D
D
All
right
thanks
so
much
peter.
Well,
I
wanted
to
preface
the
panel
by
saying
that
collido
has
a
privilege
to
work
with.
You
know
thousands
of
chains
and
networks,
many
global
blockchain
initiatives
and
I'm
really
very
honored
to
introduce
our
esteemed
speakers
today.
These
sets
of
speakers
today
represent
some
of
the
highest
standards
of
excellence.
We've
seen
in
their
solution
approaches
their
architectures
and
their
business
results,
so
we're
honored
to
have
jason
yu
who's.
D
The
ceo
of
trade
go
vinod
sharma,
the
cto
of
ascend
bit
and
job
shakrit
impact
the
head
of
engineering,
a
platform
engineering
at
ascend
bit.
So
I'd
like
to
just
go
with
each
speaker
and
ask
you
if
you
could
share
a
little
bit
about
yourself
and
the
blockchain
initiatives,
you're
leading,
and
perhaps
we
can
start
in
the
same
order
jason
if
you'd
like
to
go
first.
E
Okay,
thank
you
sophia.
Thank
you
for
inviting
me
to
join
the
meeting
as
my
honor
as
big
owner.
My
name
is
jason
yu,
I'm
ceo
of
trade
gold.
Before
I
found
I
found
treat
goal,
I
have
worked
for
sunnycam
for
almost
almost
10
years
as
the
head
of
the
risk
management
management
team
from
20
2008
to
2017.
E
from
2017
to
2019.
I
found
the
first
trading
platform
in
china.
The
name
is
crude
oil.com,
but
unfortunately
it
failed
now.
Also,
I
forgot
a
lot
of
lessons
from
from
from
that
failure,
from
especially
from
the
commodity
trading
e-commerce
platform,
from
different
angles
like
business
technology
and
the
regulations.
E
Therefore,
from
2019
I
started
the
tritical
project
and
after
two
years,
very
tough
paperwork.
The
the
company
kicked
off
officially
this
january
1st.
Our
main
product
is
to
digitize
the
call
trading
documentation
which
will
help
the
the
participants
to
enhance
their
whole
trading
process.
Clear
title
protect
the
user
data
user
data
physically
based
on
blockchain,
and
also
we
can
bridge
the
asset
and
the
capital
with
a
very
high
quality.
E
D
F
Thank
you.
So,
thanks
for
inviting,
and
essentially
thanks
to
you,
as
well
as
the
entire
collider
team,
for
the
wonderful
support
you
guys
have
been
always
been
giving
us
so
myself,
we
knows
I'm
actually
working
as
a
cto
for
bid
company
ascent
bid.
Company
is
100
own
company
by
cp
group
and
it's
a
it's.
It's
it's
under
the
column
rate,
which
is
the
probably
the
largest
in
in
entire
southeast
asia,
and
in
some
matters
it
is
actually
the
largest
at
the
global
level.
F
So
we
have
those
plans
going
on
and
we've
been
using
collido
the
platforms
plus
especially
around
the
hyperledger
firefly.
So
I
think
I'll
speak
that
about
that
later
on.
But
on
my
little
bit
of
background
before
coming
to
thailand,
I
was
based
out
of
africa,
where
I've
seen
the
the
the
the
probably
the
blend
of
technologies
on
one
extreme.
It
is
quite
outdated.
On
the
other
hand,
it's
quite
advanced,
so
I
I
don't
know,
but
normally
people
think
when
they
talk
about
africa.
F
Other
things
it's
it's
quite
outdated,
but
I've
lived
there
for
eight
years.
So
I
I
can
tell
you
it's
not
the
case,
but
now
in
in
thailand,
I
have
a
team
of
about
700
engineers,
so
my
engineering
team
is
about
700
people
and
the
the
focus
is
now
shifting
from
the
traditional
technologies
to
the
blockchain,
which
is,
I
think
we
are
under
progressive
track
and
the
the
projects
which
we
are
true.
F
D
G
I
work
in
agoda,
which
is
the
one
of
the
biggest
hotel
hotel
reservation
in
asia,
and
I
worked
with
the
open
source
project
called
openstack
yeah
in
10
years
as
agoda
we
growed
like
one
thousand
ten
thousand
percent
yeah
and
the
infrastructure.
I
can
see
the
generation
evolution
from
the
legacy
data
center
move
to
private
cloud
with
using
open
source
community.
G
I
can
join
the
community,
I
can
learn
from
the
community
and
I
also
sharing
back
to
the
community
and
after
I
moved
to
to
the
too
many
cp
group.
As
I
working
with
convenor,
I
work
to
transform
the
legacy
data
center
into
the
hybrid
cloud
data
center.
So
I
see
the
generation
of
transformation
and
now
I'm
focusing
on
the
smb
company.
D
Thank
you
job.
I
think
a
follow-on
question
for
the
node
is
some
thoughts.
I
think,
bridging
on
the
open
source
thoughts
that
kumjab
shared.
I
know
you've
run
many
projects
with
hundreds
of
engineers
and
different
capacities
around
the
world.
Can
you
share
some
thoughts
on
the
trade-offs
when
you're
building
for
writing
custom
code?
That's
proprietary
or
working
with
consultants
or
different
types
of
integrators
versus
working
with
a
large
open
source
project
like
firefly.
F
I
think
that
gives
us
a
lot
of
advantage
and
exposure
to
the
real
real
experience.
So
that's
what
we
say
normally
in
my
team
I
mean
punjab
was
aware
in
the
entire
scene,
so
we
all
really
say
that
get
real
get
life
or
you
know
that's
how
we
so
we
don't
want
to
live
in
an
artificial
life.
We
all
have
ni,
so
we
believe
in
natural
intelligence
rather
than
being
an
ai
part,
but
anyways
not
going
to
that
direction.
F
So
now,
coming
back
so
of
course,
the
open
source
pro
technologies
always
helps
you
in
a
far
more
better
compared
to
the
proprietaries,
because
the
property
technology
is
what
I
believe
in
my
experience,
not
only
here
and
from
my
entire
experience
from
last
17
years.
I
think
the
the
the
one
element
which
differentiate
the
probability
and
the
open
source
the
open
source
technology
is
always
gets
built
with
the
with
the
id
in
the
mind
to
help
and
allow
others
to
grow
along
with
that
technology
grows.
F
F
But
looking
at
what
you
want
to
build
in
terms
of
the
what
your
customer
needs,
so
you
really
focus
on
your
on
your
goals
rather
than
keep
worrying
about.
Oh,
if
I
use
this
much,
I
have
to
pay
this
much.
If
I
use
this
much,
I
have
to
pay
this
much
so
that
that
fear
that
the
cost
gets
away
because
you're
trying
to
introduce
something
to
the
market.
Where
you
want
to
try
before
you
get
confident.
F
F
So
from
that
perspective,
I
think
in
our
projects,
which
we
are
doing,
it's
really
helping
us
to
to
come
up
with
that
concept,
where
we
are
able
to
collaborate
and
share
what
we
can
share
and
and
ask
the
others
to
join,
which
is
actually
helping
us,
not
only
us
but
the
partners
as
well
as
to
try
and
test
and
then
realize
our
dreams.
What
we
want
to
do
so
I
think
those
are
the
few
things
which
I
can
mention.
D
I
think
bridging
on
a
comment
you
made
with
the
the
fact
that
there's
multiple
parties
involved-
and
this
is
decentralized-
was
wondering
jason
as
ceo
of
one
of
the
world's
newest
and
fastest
moving
trade
finance
initiatives.
How
do
you
look
at
firefly
in
terms
of
enabling
speed
to
market
and
helping
you
work
with
decentralized?
D
E
There,
oh
thank
you
sophia,
you
know,
I'm
not
an
I.t,
professor
and
also
trigo
is
not
I
I
t
company.
So
most
of
my
reason
is
from
from
I
think,
from
business
business
perspective.
You
know,
you
know,
I
think
the
the
reason
for
for
us
to
choose.
You
know
open
source
solution
to
it's
very
simple,
because
you
know
traditional
business
is
focused
focus
on
international
trading
scenario
and
so
far
the
beginning
scenario.
E
I
think
maybe
it's
a
it's
kind
of
disastrous
for
us,
because
our
clients,
especially
in
commodity
trading
industry,
always
prefer
the
technology
that
support
is
from
their
own
country.
I
know
I
know,
maybe
sometimes
from
technology
side.
It's
it's
ridiculous.
Maybe,
but
you
know
it
just
happened
every
day,
freaking
frequently,
our
clients
are
always
ask
us
to
find
a
solution
that
supported
from
from
their
local
country.
E
So
I
think
I
I
remember.
I
also
discussed
this
situation
with
steve
and
sophia
last
year
when
the
fire
firefly
1.0,
is
under
the
preparation
last
year.
I
think
the
result
for
us
is
very
clear:
the
the
only
solution
is
open
source.
So
the
answer
to
left
to
me
it's
very
very
clear.
I
asked
my
cto
to
find
a
cheap
and
fast
open
source
framework.
D
F
Yeah
sorry,
I
just
thought
of
adding
this
very
specific
example
and
specific
experience
we
have
just
I
mean
still
going
through
very
closely
related
to
the
the
firefly.
So
I'm
sure
a
lot
of
people
in
south
asia
are
aware
of
that.
In
europe
we
got
gdpr
similar
thing
in
thailand.
We
got
the
pdpa,
which
is
the
personal
data
protection
act.
F
So
in
order
to
now
meet
that,
so
I
mean
when
it
came
in.
We
were
not
sure
how
this
will
impact
our
our
projects,
but
slowly
gradually
and
as
in
when
the
chapters
got
started
unfolding.
We
we
started
realizing
that
a
lot
of
projects
and
what
we
were
doing
were
supposed
to
be
undone
unlearn
and
then
redo
and
relearn.
F
F
F
F
Imagine
the
customer
calls
in
the
call
center
hey.
I
want
you
to
be
forgotten
to
forget
me,
it's
very
simple
for
the
customer
to
call
and
say
that,
but
how
difficult
or
how
easy
or
how
tedious
it
is
for
me,
as
a
backend
person,
to
make
sure
that
I
I
comply,
because
customer
is
just
trying
to
avail
the
law
which
is
there
in
in
the
country.
F
D
Thank
you
venod.
I
think
that's
a
very
practical
example
with
business
implications,
leveraging
best
practices
in
the
technology
and
illustrating
a
second
generation
of
building
blockchain
projects
that
builds
on
a
lot
of
of
some
of
the
mistakes
in
the
first
generation
of
building.
So
now
you
can
move
faster,
more
compliant,
more
cost
effective.
I
think,
just
to
close
out
was
there
something
you
wanted
to
share
kun
job.
G
Okay,
okay,
so
as
a
snb
platform,
we're
forecasting
to
build
a
blockchain
digital
platform
and
we're
focusing
to
build
as
a
two
big
platform,
which
is
the
digital
asset
platform
and
the
trust
assessment
platform
for
the
we
can
call
as
dab
and
tab
on
the
depth.
We
build
for
digital
asset
tracking
focus
on
build
well
that
we
can
keep
the
keep
tracking
the
tangible
asset,
also
intangible
assets
that
leverage
the
ethereum
compatible
blockchain
with
the
open
source,
quorum
and
hyperledger
bases
on
the
trust
assessment
platform.
G
We
use
for
proof
the
authentic
authenticity
of
the
data
that
we
can
measure
the
trust
and
we
can
revelate
on
the
hyper
ledger
fabric
yeah
underlying
technology
and
in
the
middle.
We
think
the
interoperability
layer
is
very
important,
and
so
we
build
a
blockchain
integration
so
with
the
tooling
that
working
with
the
hyperledger
firefly
that
to
ensure
that
we
compliant
the
privacy,
security
and
compliance
yeah.
As
could
we
not
mention,
we
have
the
law
and
regulation
the
pdpa
to
be
comply
in
thailand.
G
So
we
need
to
focus
on
this
one
and
in
the
last
enterprise.
The
interoperability
for
enterprise
is
very
important
for
build
cost
domain
and
also
how
to
the
data
flow
on
off
chain
and
data
chain.
Education
yeah.
This
is
very
important.
Could
we
not?
Would
you
like
to
share
additional
thought
on
this.
F
Probably
this
is
our
own
kind
of
analogy
that
how
we
break
down
the
blockchain
so
it
may,
it
may
not
resonate
with
the
with
the
rest
of
the
world,
but
this
is
very
much
resonate
and
very
much
helpful
in
case
of
ascent
bits
that
if,
if
you
really
want
to
break
down
the
blockchain,
this
is
the
way
we
break
down
and
we
coordinate
and
organize
our
team
and
our
systems.
Thank
you,
but
blockchain
or
probably
a
collider
systems
or
firefly.
F
D
Thank
you
vinod.
I
think
multi-protocol
flexibility
and
choice.
Those
are
all
very
important
things.
We
hear
across
many
use
cases
and
I
think
really
we
feel
very
privileged
to
have
you
all
jason,
vinod
and
job.
It's
always
helpful
for
people
to
hear
about
the
use
cases
how
people
are
using
the
technology,
the
rationale
and
the
results
they're
getting
so
so
thanks.
So
much
and
we're
going
to
transition
now
to
a
live
demo
and
you'll
get
to
see
the
technology
in
action,
and
it
has
some
amazing
user
interfaces
and
experiences.
H
All
right,
thank
you,
sophia,
hello,
everyone.
I
am
nico
guyer
and
I'm
excited
to
be
able
to
show
you
firefly
today
before
we
jump
into
the
demo.
I
have
just
a
couple
of
slides
just
to
kind
of
set
the
context
for
what
we're
going
to
be
looking
at
in
the
demo.
So
we
kind
of
know
what
we're
looking
at
as
we
are
looking
at
it.
So
I'm
going
to
go
ahead
and
share
my
screen,
and
hopefully
you
can
see
my
slides.
H
Okay,
great
all
right
so
just
want
to
start
off
briefly
with
talking
about
what
we're
going
to
see
when
we
built
firefly,
we
wanted
to
create
a
really
easy
to
use
developer
experience.
We
wanted
it
to
be
quick
and
easy
for
people
to
get
started
with.
We
wanted
the
experience
to
be
powerful
enough
to
meet
the
needs
of
experienced
web
3
developers,
but
also
kind
of
you
know
help
people
get
started,
who
maybe
this
is
their
very
first
web
3
project.
H
We
wanted
to
use
tools
that
felt
familiar
and
we
also
wanted
it
to
be
able
to
run
everything
offline
on
a
laptop.
Even
if
you
are
you
know,
on
an
airplane,
you
can
you
can
work
on
building
an
app
against
fireflies
api
completely
offline,
once
you've
downloaded
everything
ahead
of
time.
So
that's
the
developer
experience
that
we're
going
to
see
so
here's
what
we're
going
to
run
today,
I'm
going
to
run
the
firefly
cli
and
I'm
going
to
create
a
local
developer
environment
on
my
machine.
H
This
is
using
all
open
source
tools.
These
are
all
you
can
find
the
source
code
for
all
these
tools
in
the
hyperledger
firefly.
Get
repos
so
that
the
cli
behind
the
scenes
will
use
docker
compose
to
run
all
of
the
components
of
a
super
node
right
on
my
laptop.
So
what
does
that?
Look
like
here's
a
little
picture.
This
is
a
picture
of
two
different
super
nodes
that
we're
going
to
be
running.
I'm
actually
going
to
be
running
three.
H
I
didn't
show
the
third
one
here
just
for
the
sake
of
space,
but
within
our
super
node
there
is
a
firefly
core,
and
this
is
the
brain
that
peter
was
talking
about
earlier.
This
is
the
orchestration
engine
that
and
it
also
provides
the
api
layer
and
it
also
hosts
the
web
ui
layer
that
we'll
be
looking
at
as
well.
H
The
firefly
core
talks
to
a
lot
of
different
systems.
Each
of
these
is
going
to
be
running
in
a
different
docker
container
on
my
machine,
including
a
database,
a
data
exchange,
a
blockchain
node,
a
tokens
connector
and
a
variety
of
other
things
outside
the
supernode.
We
are
also
going
to
be
running
an
application
called
the
firefly
sandbox
for
each
member
of
this
firefly
network
that
we're
going
to
be
building
here
now,
the
firefly
sandbox.
You
can
think
of
as
an
application,
an
end
user
application,
that's
written
to
use
fireflies
api.
H
So
it's
both
an
example
of
you
know
how
you
can
build
an
app
and
it
also
provides
code
snippets
that
you
can
use
to
copy
and
paste
into
a
backend
application
using
the
firefly
sdk
to
build
your
own
app
okay.
So
this
is
kind
of
the
topology
of
what
we're
going
to
look
at
so
we're
I'm
going
to
be
running
firefly
in
what
we
describe
as
a
sort
of
a
multi-party
network,
a
multi-party
mode
where
there
are
multiple
firefly
nodes.
H
So
we're
going
to
look
at
the
firefly,
dashboard
and
and
the
firefly
sandbox,
those
are
screenshots
of
them,
but
even
better
than
a
screenshot
is
actually
seeing
the
real
thing.
So,
let's
hop
over
to
my
other
desktop
here,
this
is
the
firefly
explorer
or
the
firefly
ui.
This
is
a
web
front
end
that
is
being
hosted
by
firefly
core
and
it's
sort
of
an
inspector,
a
view
into
the
system.
H
H
Just
so
we
can
visually
compare
so
here's
our
network
map.
Right
now,
I
haven't,
run
any
transactions
on
this
network.
So
that's
why
you're
seeing
no
activity,
but
let's
do
some
transactions.
Now,
I'm
going
to
open
a
new
tab
and
I'm
going
to
open
the
firefly
sandbox.
Actually,
what
before
I
do
that?
H
What
I
didn't
show
you
is
that,
while
before
I
started
sharing
my
screen
on
my
other
desktop
here,
I
have
I've
run
the
firefly
cli
and
I've
started
a
network
of
three
members
and
it
prints
the
urls
for
the
web
ui
and
for
the
sandbox
for
each
of
these
members-
and
that's
that's-
those
are
the
urls
that
I
opened
in
my
browser
separately.
I've
also
deployed
an
erc20
and
the
erc
721
contract
to
this
chain
on
the
right
hand,
side
of
my
screen,
you
can
see
the
solidity
source
for
the
erc20
contract.
H
It
is,
it
extends
and
opens
up
one
erc20
contract,
and
it
adds
just
a
little
bit
of
custom
functionality
on
top
of
that
to
be
able
to
mint
and
transfer
tokens
with
data.
So
we'll
come
back
to
this
in
just
a
little
bit,
but
what
I
want
to
show
you
first
is
the
firefly
sandbox
so
like
I
said
this
is
both
an
example:
end
user
application
that
and
and
also
shows
you
kind
of
how
to
build
each
of
the
different
things
that
you
can
do
with
firefly
into
your
own
application.
B
H
H
You
know
apps
flows
and
and
digital
assets.
These
these
can
be
grouped
into
these
three
categories
here.
So
what
I
want
to
start
with
is
custom
contracts,
because
that's
that's
the
thing
that
people
oftentimes
think
of
first,
when
they
think
of
hey.
I
want
to
build
a
blockchain
application.
Oh,
I
need
a
custom
smart
contract.
How
am
I
going
to
do
that?
H
H
It
could
be
something
entirely
different.
What
I'm
going
to
do
first,
is
I'm
going
to
define
a
contract
interface.
A
contract
interface
in
firefly
is
a
way
to
describe
a
custom.
Smart
contract
or
any
smart
contract
in
a
blockchain
generic
way,
so
it
encapsulates
important,
specific
blockchain
information,
but
it
also
describes
the
entire
contract
in
a
way
that
firefly,
I
could
describe
both
a
solidity
contract
or
a
fabric
chain
code
using
a
firefly
interface
so
for
blockchains
that
have
a
built-in
format
to
describe.
H
H
Into
firefly
to
automatically
do
this
conversion
for
you.
So
if
you
have
the
api
for
your
contract,
you
can
actually
copy
that
right
into
the
firefly
sandbox,
which
is
what
I'm
going
to
do
here.
So
I'm
going
to
pick
api
celebrity
application,
binary
interface,
I'm
going
to
go
back
over
to
my
source
code
and
after
I've
compiled
the
contract,
I
get
a
json
output
and
I'm
just
going
to
copy
the
api
here.
G
H
H
And
I'm
just
going
to
paste
that
right
here,
I'm
going
to
give
this
fire
this
contract
interface,
a
name
we'll
call
this
just
erc
20
with
data
and
we'll
say
this
is
version
1.0
and
I'm
going
to
run
this.
What
happens
when
I
run
this
we'll
see
off?
On
the
right
hand,
side,
there
are
some
things
going
on
so,
but
before
before
we
look
at
the
events
immediately
we
get
back
a
202
accepted.
H
We
get
an
id
here
that
we
can
use
to
track
that
request
through
the
system.
So
firefly
has
a
very
asynchronous
programming
model,
that's
event
driven,
and
so,
when
you
submit
things
to
the
system,
if
the,
if
it
is
accepted
into
the
system,
you'll
get
a
202
and
an
id
back
and
then
the
the
general
pattern
is
that
you
either
have
a
websocket
or
web
hooks
that
are
listening
for
events
coming
out
of
firefly.
So
in
this
case
we've
received
some
events.
H
Those
events
indicate
that
we
have
broadcasted
this
firefly
interface
to
all
of
the
other
members
of
the
system,
and
so
what
this
means
is
now
the
we
can
go
into
our
our
dashboard.
I
can
reload
this
and
we'll
see
that
there
was
a
batch
pin
transaction
that
happened.
Let's
go
look
at
the
in
off
chain.
We
can
look
at
data
and
we
can
see
there
was
a
definition
that
was
created
here,
and
this
is
the
definition
of
my
smart
contract
that
I
just
uploaded.
Well,
that's
great.
H
We
submitted
it
so
it's
appearing
in
our
dashboard,
but
because
it
was
broadcasted
to
all
the
other
members
of
the
network.
I
could
hop
over
to
the
blue
node
as
well,
and
I
could
look
at
the
off
chain
data
tab
here
and
I
can
see
the
same
definition
so
when
we
create
a
definition
in
a
firefly
network,
it's
a
way
of
defining
a
piece
of
data
or
or
defining
some
sort
of
structure
that
all
the
members
of
the
network
should
know
about.
H
In
this
case,
it's
this
contract
that
all
of
these
members
will
be
interacting
with
here
shortly.
So
that's
great!
Now,
how
do
we
actually
use
our
contract?
So
the
next
step
is
to
build
an
api
endpoint
for
it.
So
to
do
that,
we're
going
to
register
a
contract
api,
we're
going
to
select
the
contract
interface
that
we
just
created
here
and
I'm
going
to
call
this
erc20
and
then
I
need
to
give
it
the
contract
address.
H
As
we
can
see,
we
we
received
an
event
that
the
message
was
confirmed
and
now
what
this
has
done
is
this
has
built
an
api
endpoint
that
we
can
use
to
interact
with
our
smart
contract
in
addition
to
just
creating
endpoints.
It's
also
created
full
open
api,
three
spec
and
a
swagger
ui
that
we
can
open
and
we
can
interact
with
our
contract
right
here
in
our
browser.
So,
let's
mint
some
tokens
now
I
can
invoke
methods
on
the
contract,
so
I
can
invoke
mint
with
data.
H
I
can
click,
try
it
out.
Let's
mint
a
thousand
now
we
can
send
some
data
with
it,
because
this
is
our
custom
mint
with
data
function.
I
don't
need
to
send
any
particular
data
right
now,
so
I'm
just
going
to
use
a
null
hex
string
and
then
I
need
to
provide
the
two
address.
This
is
the
ethereum
address
that
I
want
to
make
these
tokens
to
I'm
going
to
make
them
to
myself
for
now.
H
So
to
find
my
ethereum
address
for
the
red
node,
I'm
going
to
go
back
to
the
firefly
explorer
and
I'm
going
to
look
at
the
network
under
organizations
in
the
network.
I
can
see
the
list
and
I
can
see
this
is
my
my
org
or
your
org.
That's
what
it
says,
I'm
going
to
click
here
and
then
under
the
verifiers
section,
there's
an
ethereum
address,
and
this
is
the
address
of
the
wallet
for
the
signing
key
for
the
red
node
in
the
network.
H
I'm
going
to
go
back
to
the
sam
sorry
to
my
swagger,
ui
and
paste
that
here
and
I'm
going
to
click
execute
so
immediately.
We
get
a
202
back
and
what
I'm
also
going
to
do
now
is
we're
also
interested
in
when,
when
tokens
are
transferred
on
the
network,
it
would
be
great
to
receive
events
for
those
as
well.
H
I'm
going
to
do
a
query
now
this
is
a
read-only
operation.
Click!
Try
it
out!
I'm
going
to
paste
again
my
my
address
here
and
we
should
see
we
have
a
thousand
yep.
We
do
okay,
great!
So,
let's,
let's
do
a
transfer
real
quick
and
we
should
see
that
event
come
in,
so
we're
gonna
go
back
up
here
to
and
we're
gonna
invoke,
because
this
will
perform
a
blockchain
transaction.
Try
it
out,
let's
send
100
and
let's
get
the
address
of
the
green
node
this
time.
H
So
again,
we'll
go
back
to
the
dashboard
look
under
organizations
and
under
the
verifiers
we'll
get
the
ethereum
address
of
the
green
node
and
we'll
paste
that
here,
okay,
we
get
a
202
back,
let's
go
check
the
balance
of
the
green
node
down.
So
we'll
go
back,
let's
scroll
back
down
here
to
query
the
balance
of
it.
H
Let's
check
our
own
balance,
first,
just
to
make
sure
yep.
So
now
we
only
have
900
and
we'll
check
the
green
node
and
the
green
node
has
a
hundred
okay,
that's
great!
Let's
take
a
peek
back
at
the
sandbox
we
receive.
We
see
that
while
we
were
doing
that,
we
received
some
blockchain
events,
and
that
was
because
we
set
up
that
contract
listener.
We
can
start
receiving
events
from
this
custom.
Smart
contract
as
well.
Let's
go:
take
a
look
at
the
firefly
explorer
and
see
what
was
going
on
inside
firefly.
H
While
we
were
doing
all
these
things,
so
we
can
look
at
the
blockchain
dashboard.
We
can
see
that
there
were
several
batch
pin
events
from
broadcasting,
the
the
contract
and
the
api.
We
can
also
see
that
there
were
two
transfers
here
as
well.
One
was
the
actually
the
mint
because
mint
actually
just
does
a
transfer
behind
the
scenes,
and
the
other
was
was
the
transfer
of
the
100
tokens
to
the
other
node.
H
So
we
can
click
on
it
and
see
the
output
see
it
was
from
this
address
to
this
address
and
we
transferred
behind.
So
that's
great,
I
realize
I'm
running
out
of
time
here,
so
I'm
gonna,
I'm
gonna,
try
to
speed
things
up
here
a
little
bit,
but
this
is
the
sort
of
the
kind
of
the
building
blocks
of
being
able
to
work
with
custom,
smart
contract
logic
with
firefly
and
just
really
developer
friendly
apis.
C
H
Earlier
hypothetically,
what
if
this
was
a
token
contract?
That's
been
on
chain
on
a
public
chain
as
an
example,
for
you
know,
maybe
even
years
and
there's
a
lot
of
transactions
on
there,
and
we
want
to
build
a
history
of
what
has
already
happened
on
this
chain.
That's
where
the
firefly
token
connector
comes
into
play
and
that's
where
the
concept
of
a
firefly
token
pool
is
used.
So
to
do
that,
even
though
this
contract
has
only
existed
for
about
five
minutes
and
we've
only
had
two
transactions
on
it.
H
H
So
now,
if
we
go
back
and
look
at
our
explorer,
we
can
go
to
the
tokens
tab
here.
Under
the
token
section,
we
can
look
at
the
dashboard,
and
now
this
is
a
brand
new
page.
That's
just
lit
up,
because
we've
created
this
token
pool.
We
can
see
account
balances
for
everyone
that
has
a
balance
on
here
and
you'll
notice
that
there's
a
lot
of
zeroes
here.
H
H
Likewise,
the
firefly
sandbox
also
provides
ways
to
mint
and
transfer
right
here
right
in
the
sandbox
ui.
So
you
you
could
go
straight
to
here
and
you
don't
have
to
actually
interact
directly
with
the
the
swagger.
If
you
wanted
to,
I
just
wanted
to
show
that
sort
of
building
up
from
a
custom
smart
contract
all
the
way
to
these
rich
tokens
apis
now.
So,
let's
mint
a
hundred
now
again,
this
is
this
is
going
to
be
100
times
18,
just
because
of
the
the
way
this
is
represented
in
the
user
interface.
H
H
For
the
sake
of
time,
I'm
just
going
to
kind
of
scoot
through
this
here
a
little
bit
and
then
finally,
let's
burn
one
just
so
we
can
see
what
that
looks
like
in
the
dashboard.
So
I
ran
several
different
token
transactions
there.
Let's
hop
back
over
to
the
explorer
and
refresh
now
we
can
see
our
new
account.
Balance
has
been
reflected
immediately
here
and
we
can
see
the
the
the
other
transfer
you
can
see
who
it
was
from
to
the
signing
key.
H
So
some
amazing
things
just
make
it
super
easy
to
do
stuff
with
tokens.
I
don't
have
time
to
also
show
non-fungible
tokens,
but
you
can
do
all
the
same
things
with
non-fundable
tokens
as
well
through
here
and
it's
it's
really
powerful,
really
easy,
quick
to
get
up
and
started
the
last
thing
that
I
want
to
touch
on
just
real,
quick
and
then
and
then
we'll
do
some
q.
A
is
messaging
messaging
is
a
foundational
component
in
firefly,
it's
a
it's
a
very
foundational
component
in
building
distributed
applications.
H
I
have
data
on
one
system
that
I
need
to
send
to
another
party
or
to
another
system
that
could
be
a
simple
string.
It
could
be
a
json
object.
It
could
be
a
json
object
that
conforms
to
a
certain
json
schema
that
I've
defined.
That
is
represents
an
important
type
that
members
of
the
multi-party
network
have
agreed
upon
and
it
could
be,
it
could
actually
just
be
a
file
as
well.
H
I
could
click
here
and
I
could
upload
a
file
directly
to
here
so
for
this
I'll
just
send
a
string,
so
this
is
going
to
be
a
broadcast
message.
Yeah
just
like
when
I
was
broadcasting
the
firefly
interface.
This
is
just
going
to
broadcast
a
strength
to
everyone.
So
I'll
run
this
I'll
wait
for
my
batch
pin
to
be
confirmed
here
and
then
let's
go,
take
a
look
at
the
blue
node.
Here
we
should
see
under
under
off
chain
data,
which
is
where
we're
at
already.
H
Actually,
I
could
click
here,
and
here
is
a
message:
let's
take
a
look
at
the
green
node
and
look
at
octane
data
as
well,
and
here
is
the
message
as
well.
So
in
these
cases,
as
someone
mentioned
in
the
chat
earlier,
yes,
the
there
is
a
blockchain
transaction
and
the
the
payload
of
the
message
is
hashed
and
it's
pinned
to
the
blockchain.
The
actual
payload
remains
off
chain.
It
remains
in
a
shared
storage
mechanism,
and
this
is
what
we're
seeing
here.
This
is
what's
why
the
data
is
under
the
off
chain
tab
here.
H
H
Indeed,
there's
our
secret
message
we
sent
to
green
should
be
able
to
see
it
in
green's
dashboard
there.
It
is,
but
if
we
go
back
and
look
at
blue's
dashboard,
we'll
we'll
notice
that
the
blue
node
does
not
see
that
message
at
all.
So
that's
just
a
really
quick
snapshot
of
messaging
messaging
is
really
important.
There's
there's
a
lot
of
different
features
in
it
as
well.
H
I
don't
have
time
to
go
into
all
of
them,
but
hopefully
this
was
just
a
a
very
quick
taste
of
some
of
the
things
that
you
can
do
with
firefly
and
gives
you
an
idea
of
how
you
can
get
up
and
started
with
it.
There
are
guides
in
the
documentation
that
will
walk
you
through
using
a
firefly
cli,
installing
a
firefly
cli
using
it
to
set
up
this
same
environment
that
I
just
built
running
the
firefly
sandbox
and
begin
walking
you
through
each
of
the
three
sections
of
messages,
tokens
and
contracts.
H
H
A
Okay,
well,
first
of
all,
thank
you
all
for
the
for
the
presentation.
It's
very
helpful
and
I'm
very
excited
about
it.
I
I've
actually
been
exploring
firefly
for
some
months
at
this
point,
so
I
continue
to
be
very
excited
about
it.
To
get
to
the
question,
so
there's
been
some
discussion
about
the
multi-chain
reality
of
the
future,
and
I
certainly
agree
with
that.
It's
it's
becoming
very
central,
very
quickly
to
the
work
that
I
do.
A
A
Is
there
now
or
are
there
plans
to
integrate
support
for
some
of
the
zero-knowledge
proof-based
flows
and
interactions
generally,
that
that
would
facilitate
this
kind
of
not
just
cross-chain
but
sophisticated
privacy
enhancing
or
privacy,
retaining
even
interactions
that
are
not
possible
without
zero
knowledge,
proof
technology
yeah
thanks
paul.
That
was,
I
think,
three.
H
Questions
which
is
about
the
limit
of
what
I
can
remember
all
at
one
time
but
I'll
take
a
stab
at
the
first
two
first
was:
does
firefly
currently
connect
to
a
single
blockchain
as
a
firefly
1.0?
What
I
was
demonstrating
was
all
of
the
all.
The
messaging
and
orchestration
primarily
messaging
does
happen
on
a
blockchain,
but,
like
you
said
that
could
be,
it
is
pluggable,
so
it
could
be
fabric,
it
could
be
ethereum
and
that
ethereum
could
be
go
ethereum.
It
could
be
baisu
it.
H
It
is
plugable
that
you
could
use
additional
chains
through
the
token
connectors
today.
So
that's
that's
kind
of
the
state
of
fireflight
1.0.
Today
there
is
a
lot
of
work
going
on
actively
in
the
code
base
right
now
in
the
firefly
community
to
allow
connections
to
multiple
chains
for
for
various
for
different
purposes,
including
including
public
chains
as
well
peter.
C
C
C
Hundreds
of
thoughts
to
share
with
you
there
very
much
a
a
plug
point
for
firefly
that
we,
the
tokens
connect
in
particular,
is
a
great
place
to
plug
that
in
jim
who's.
On
the
line,
and
I
have
had
lots
of
conversations
about
the
projects
that
could
plug
in
there.
There
is
not
one
on
the
shelf
in
the
open
source
community
that
you
can
use
as
a
plug
point
today,
but
there
is
there's
been
a
lot
of
thinking
and
a
lot
of
experimentation
in
that
space.
B
H
H
It's
it's
very
easy
to
set
up
the
the
very
same
thing
that
I
just
demoed
here
today
and
so
so.
We've
seen
a
lot
of
people
in
the
community
coming
to
to
blockchain
they're
new
to
blockchain
or
they're
new
to
web3,
and
they
firefly
is
sort
of.
We
talk
about
it
being
a
a
web,
3
gateway
as
a
as
a
component
in
an
architectural
stack,
but
in
a
lot
of
ways
it's
it's
a
developer's
gateway
into
their
first
experience
with
building
a
web3
app
as
well.
So
so
firefly
is
not
a
blockchain.
H
It's
not
a
distributed,
ledger
technology,
but
it
provides
a
layer
on
top
of
the
dlt.
It
provides
a
layer
on
top
of
distributed,
storage
and
a
bunch
of
other
pretty
complicated
topics
that
present
a
very
easy
to
use
api,
and
so
hopefully,
you're
able
to
see
that
from
the
demo
but
yeah
it
is.
It
is
a
great
place
to
to
to
come
to
to
learn
to
just
try
like
hey.
I
want
to
learn
about
erc20
or
I
want
to
learn
about.
C
I
would
encourage
everybody
who's
looking
to
get
into
blockchain.
There
isn't
a
bad
place
to
start.
One.
One
particularly
good
place
to
start
is
to
try
out
tokens
that
they're
just
such
a
ubiquitous
like
it.
It's
it's
so
core
to
sort
of
a
value
that
you
can
get
from
blockchain,
it's
so
hard
to
build
anything
else,
and
you
can
really
learn
about
what
blockchain
can
do
with
them
and
because
they're
so
well
adopted.
There's
great
standards
out
there
and
a
project
like
firefly
has
pre-built
connectors
for
a
whole
bunch
of
standards.
C
The
rc-20
c721
erc
1155.
So
you
don't
have
to
start
in
solidity.
You
can
start
by
trying
out
what
the
contract
does
out
the
box,
and
then
you
can
try
extending
the
solidity
a
little
bit.
You
don't
have
to
start
from
scratch
so
that
that's
a
really
good
tip
for
anybody
who's
looking
to
get
into
blockchain
for
the
first
time.
B
Yeah
thanks.
Thank
you
both
and
one
related
question
is
like
I
was
recently
developing
a
d
app
and
which
talks
to
salesforce.com
salesforce.com
is
a
cloud
computing
fast
platform,
so
I
was
trying
to
use
ether.js
to
connect
it
via
javascript,
but
with
the
firefly
I
see
there's
a
way
to
expose
apis
which
maybe
can
be
consumed
with
a
backend
system
like
which
is
not
dependent
on
metamask.
C
Music
to
our
ears,
I
I
come
from
an
integration
background,
so
you're
speaking
my
language
and
and
being
able
to
sort
of
point
none
blockchain
technologies
at
something
that
looks
the
way
that
they
understand
the
world.
Predictable,
apis,
predictable
events,
you
know,
maybe
you've
got
an
enterprise
service
bus
and
it's
like
you
need
something
you
can
connect
that
to
firefly
speaks
that
language
on
one
side
and
it
speaks
blockchain
on
the
on
the
other.
So
you
should
find
it
a
really
great
toolkit
to
build
something
like
a
salesforce
connector
in
there.
B
C
C
B
B
I
I
If
you
want
to
use
golang,
you
can
try
out
hyperledger
fabric
instead,
which
firefly
also
supports.
In
fact,
you
can
use
nico's
cli
to
provision
a
full
fabric
network
and
build
firefly
components
on
top
of
it.
Just
on
your
laptop,
you
just
need
to
provide
the
fabric
as
the
blockchain
provider,
and
there
you
can.
C
And
just
to
add
to
what
jim
said,
because
fabric
doesn't
have
a
definition
format
for
what
inputs
look
like
to
a
smart
contract
function,
you
you
do
craft
sort
of
fireflies,
adding
that
value
to
fabric
directly.
There
isn't
one
underneath
it
fabric.
Just
it
it's
bytes
is,
is
the
input
for
an
individual
function,
but
you
can
use
it
to
say
actually,
my
go.
Smart
contract
expects
a
json
payload
for
the
first
parameter
with
these
parameters,
and
it's
not
a
lot
of
work
to
craft
that
from
scratch.
C
B
C
I
A
For
what
it's
worth
fabric,
by
virtue
of
at
least
potentially
communicating
with
chain
code
via
grpc,
could
potentially
take
advantage
of
grpc's
server,
reflection,
service
or
server
reflection,
apis,
which
support
dynamic,
querying
and
invocation
of
grpc
functions.
Rpc
calls
or
streaming
by
by
reflection
at
runtime.
A
Yeah,
if
you
can
invoke
you
know
proto-c
on
the
fly
you
know
also
at
runtime.
That
might
also
work.
If,
if
you
can
dynamically
link
the
results,
I
think
you
can
do
that
in
some
languages,
but
not
others.
That
would
be
the
concern
that
I
would
have
about
that
approach.
I
would
look
at
server
reflection
closely,
but
of
course
that
that
then
is
up
to
the
chain
code
developer,
that's
not
something
that
fabric
can
enforce
or
firefly
can
enforce.
I
C
It's
great
to
have
you
in
the
community,
paul
and
and
and
everybody
on
the
call.
I
know
we've
probably
run
out
of
time
for
questions
here,
but
do
jump
on
the
discord
engage
with
us.
Get
involved
friendly
bunch
that
there's
lots
of
people
there
keen
to
to
help
and
and
chat
through
what
you're
trying
to
achieve
and
help
there.