►
Description
A virtual meetup hosted by Hyperledger NYC featuring Gary Crisci from General Electric will discuss the challenges that GE faced and how they overcame them when implementing their blockchain solution to improve inter-company transactions. Robert van Donge from IntellectEU will then speak about the company's previous experiences in working with enterprise blockchain and what led them to work on the Catalyst Blockchain Platform, a platform-as-a-service solution that aims to simplify the creation and management of blockchain networks. Following these two presentations, there will be a collaborative Q&A discussion with the audience.
More about the event is at: https://www.meetup.com/Hyperledger-NYC/events/273886285/
----
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
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 #HyperledgerMeetups #Blockchain
B
D
Yeah
yeah,
absolutely
people
will
take
a
couple
minutes
to
trickle
in
I
did
get
the
youtube
live
stream
going
again.
We
we
usually
see
a
good
pick
up
there
about
10
to
15
additional
people,
and
there
is
a
chat
also
on
youtube.
So
when
you
get
to
the
q
a
yet
if,
if
anybody
wants
to
just
keep
an
eye
over
there
and
bring
questions
in
here,
that
would
be
great,
and
let
me
now
set
you
as
host.
D
C
C
C
C
We're
currently
recording
live
on
youtube,
and
we
would
ask
that
you
ask
any
questions
either
in
the
chat
here
on
the
zoom
call
or
on
the
youtube
page,
and
I
will
be
addressing
those
questions.
You
know
at
the
end
of
each
presentation,
but
I
think
right
now
we
can
get
started
and
gary
the
floor
is
yours.
B
Great
thanks
so
much
chris
and
welcome
everybody
thanks
for
joining
today
glad
you
could
be
here.
This
is
a
great
opportunity
to
share
some
information
that
we
have
about
a
proof
of
concept,
project
that
we
worked
on
and
and
where
we
are
today
with
our
learnings
from
that,
and
I'm
excited
to
do
this
for
the
hyperledger
community.
B
I've
done
this
presentation
a
few
different
times,
and
some
different
forums
had
some
plans
to
do
some
out
on
the
road
and
unfortunately,
due
to
the
pandemic
that
that
kind
of
disrupted
those
plans.
So
I'm
happy
to
see
that
we're
doing
these
virtual
events
and
we're
still
able
to
get
out
there
and
share
this
information.
B
So
I'm
gonna
run
through
some
slides
here
and
talk
about
what
we
did
in
this
project.
First
off
just
you
know
a
little
bit
about
ge.
I
assume
many
people
have,
if
not
most
of
you
have
heard
of
general
electric
been
around
for
a
very
long
time,
operates
in
a
number
of
different
verticals
and
industries,
primarily
in
aviation
and
healthcare
and
energy.
B
So
those
are
some
of
the
key
areas
that
we
focus.
I
actually
work
at
ge.
Corporate,
which
is
the
parent
organization
over
the
different
business
units,
so
a
little
bit
about
myself,
I'm
principal
architect
at
ge
corporate,
and
you
can
look
me
up
on
linkedin.
I
have
my
colleague
francisco
ponte
on
here.
He
usually
does
this
presentation
with
me
today
I'll
be
flying
solo.
B
B
I'm
gonna
do
an
introduction
to
blockchain
and
hyperledger
fabric,
I'm
going
based
on
the
premise
that
most
people
on
this
call
have
a
have,
a
pretty
good
foundation
in
what
blockchain
is
and
what
hyperledger
fabric
is
specifically,
but
I
will
touch
on
that
and
we
can
even
dig
into
it
a
little
deeper
in
the
q.
A
for
those
of
you
who
who
are
more
experienced
I'll
review
the
solution.
Architecture
we'll
talk
about
analytics
on
top
of
blockchain,
which
was
a
key
component
of
what
we
did
here.
B
Blockchain
itself
is
is
one
piece
of
a
broader
solution
to
the
entire
problem,
so
we're
gonna
talk
about
analytics
and
then
we'll
do
the
closing
and
the
q
a
okay.
So
the
challenge
was
to
modernize
our
internal
billing
system,
and
so
today
ge
uses
a
centralized,
mainframe
application.
So
about
25
plus
years
old,
we
run
about
four
million
invoices
intercompany
invoices
through
this
system
every
year
and
like
many
mainframes.
B
So
what
we
wanted
to
look
at
was
what
could
we
do
with
a
distributed
ledger
to
solve
for
this
problem
right?
And
so,
if
we
looked
at
integrating
the
finance
systems,
we
wanted
a
mobile
first
front
end.
We
wanted
to
do
a
microservice
architecture,
dispute
management
platform
which
we
didn't
have
and,
as
I
mentioned
earlier,
smart
analytics,
okay.
B
So
the
first
thing
we
did,
we
kind
of
took
a
page
out
of
our
enterprise
architecture,
handbooks
and
said:
well,
let's
start
off
with
the
capabilities
model
right
and
I'll,
even
take
a
step
back
to
just
say.
You
know
this
is
kind
of
the
functional
slide
right.
So
for
those
of
you
who
are
unaware,
I
mean
I
should
probably
take
a
quick
step,
a
quick
second
to
explain
what
is
an
inter-company
transaction
right.
B
B
Okay,
so
within
the
capabilities
model
here
you
can
see
this
was
kind
of
the
functional
approach
of
what
does
the
application
need
to
do,
and
there
was
some
color
coding
in
here
around
things
that
the
current
system
does
things
that
are
nice
to
have
things
that
are
must
have,
and
and
so
how
we
could
approach
that,
and
so
we
broke
it
out
into
these
different
pillars,
and
we
had
these
different
tests
that
the
new
system
would
have
to
do,
because
it's
also
a
good
time
to
mention.
We
did
not
just
evaluate
blockchain.
B
B
Okay,
so
moving
along
into
the
blockchain
solution.
This
is
the
design
overview
we
came
up
with
and
if
we
look
at
kind
of
that
capabilities
model
and
how
would
we
kind
of
take
those
requirements
and
feed
them
into
different
tiers
within
a
blockchain
solution?
So
we
really
looked
at
wing
to
wing
you'll,
see
as
I
go
through
the
solution.
Architecture
blockchain
is
just
a
piece
of
it
and
that's
important
to
recognize.
B
B
B
B
B
Did
they
do
something
malicious?
Were
they
trying
to
steal
money
from
that
other
organization
that
other
entity
that
other
cost
center?
No,
they
probably
just
didn't,
get
to
it,
and
so
what
we
can
do
in
in
terms
of
using
smart
contracts
and
the
way
we
set
up
the
these
rules
is
we're
able
to
ensure
that
we
get
things
right
at
inception,
that
we
really
have
process
integrity
based
on
those
rules
and
everything
is
transparent
and
visible
to
everybody
else
which
takes
us
into
our
next
column.
B
This
idea
that
why
does
corporate
need
to
be
the
central
point
of
authority
for
two
businesses
to
have
to
come
to
so,
if
business,
a
submits
a
transaction
in
business
b,
says
that's
no
good.
Why
do
they
have
to
mediate
that
through
corporate
right?
So
as
we
look
at
transparency
of
everybody
sees
everything
plus
no
intermediaries,
these
things
run
faster
and
at
a
lower
cost.
B
If
you
get
to
interact
with
each
other
directly
corporate's,
just
another
participant
right
treasury
is
just
observing
this
activity
and
they're
being
queued
up
to
settle
cash
exchange
at
the
end
of
the
month
or
whatever.
The
period
is
when
they
choose
to
do
a
cash
settlement.
Okay
and
lastly,
was
automation
again,
these
real-time
reconciliations.
B
Today,
reconciliations
are
done.
It's
a
time-consuming
process,
people
on
one
side
of
the
transaction
upload
their.
What
they
believe
is
the
the
record
and
the
truth,
other
side
uploads
theirs,
and
then
it
has
to
be
reconciled.
And
if
it's
incorrect,
everybody
has
to
go
back
and
try
to
figure
out
what
went
wrong
so
being
able
to
have
a
you
know
this,
real-time
reconciliation.
B
We
eliminate
a
lot
of
those
errors.
We
have
continuous
visibility
into
the
positions
where
we
are
and
some
of
the
things
that
we
didn't
explore
in
this
proof
of
concept,
but
that
I
put
forth
as
potential
down
the
road
is
integrating
additional
emerging
technologies
like
machine
learning
and
ai,
to
evaluate
currency
translation
rates
and
advise
and
and
send
notifications
when
it's
an
optimal
time
to
do
those
cash
settlements
so
beyond
just
doing
them
at
a
scheduled.
Well,
let's
just
do
them
on
the
15th
of
the
month,
because
that's
how
we
always
do
it.
B
Okay,
so
looking
at
different
blockchain
models,
as
we
start
to
you,
know,
move
the
conversation
in
the
direction
of
hyperledger.
It's
you
know
when
I
talk
to
different
people
about
this,
we
want
to
be
very
clear:
we're
talking
about
enterprise
blockchain
right,
we're
not
talking
about
permissionless
anonymous
public
blockchains,
we're
not
talking
about
cryptocurrency
right.
This
is
not
about
bitcoin
and
to
clarify
further
on
the
cryptocurrency.
B
B
We've
had
abstract
conversations
and
brainstorming
sessions
about
that,
but
that's
not
where
we
were
going
with
this
at
this
time.
This
was
more
just
about
a
distributed,
ledger
and
being
able
to
do
the
reconciliations
in
the
currencies
that
they're
in
today
again
future
use.
Potentially
you
could
look
at
integrating
your
own
crypto
coin
or
token
as
a
way
of
also
doing
the
reconciliations
and
settlements.
B
Okay,
so
again,
we're
in
this
bucket
over
here
of
consortium.
Federated
users
are
known.
You
know
we
have
permission
for
who
can
do
what
we
use
a
voting
multi-party
consensus
right,
we're
not
using
any
kind
of
proof
of
work,
consensus
or
anything
like
that.
It
would
be
way
too
slow
for
the
for
our
volume,
so
using
kind
of
the
kafka
and
raft
type
of
consensus
mechanisms
that
you
find
in
hyper
ledger
lighter
faster,
that
that
was
more
in
line
with
what
we
were
looking
at.
B
So
looking
at
hyper
ledger,
what
is
hyper
ledger
fabric
again
if
you're
on
this
call?
I
think
you
probably
have
a
pretty
decent
idea.
Hopefully
you
do.
Obviously
this
is
an
open
source,
blockchain
platform
from
the
linux
foundation.
It
started
early
on,
I
believe,
with
ibm
and
and
some
other
players
that
came
in
the
code
was
handed
off
to
linux
foundation,
to
be
maintained
and
and
and
built
upon,
to
run
the
consortium
again
down
at
the
bottom.
B
No
cryptocurrency
required
right
modular
architecture,
which
is
very
important
for
some
of
the
different
pieces
that
we're
going
to
be
talking
about
channels.
Private
data
collections
very
useful
for
again
the
type
of
work
we're
doing,
because
if
I
have
four
or
five
different
companies,
company
a
and
company
b
are
doing
transactions.
Company
c
doesn't
really
need
to
be
privy
to
that
or
tied
up
in
that,
so
channels
are
very
effective
way
of
being
able
to
segment
that
work
and
segregate
it.
B
Okay,
so
lots
of
different
abilities
here
that
we
thought
hyperledger
fabric
was
really
the
right
solution
for
us.
Obviously,
there
are
other
ones
to
consider
the
other
two
main
ones
that
that
we
kind
of
tossed
some
ideas
around
were
ethereum
and
quorum.
Wait,
no,
not
quorum.
Quarter.
Quarter,
I
think
that
was
it
so
ethereum
was
the
other
main
one
though,
but
ultimately
hyperledger
fabric
really
fit
in
with
what
we
wanted
to
do.
B
The
ability
to
do
smart
contracts
chain
codes
right.
This
really
comes
down
I've.
My
career
is
built
in
financial
systems,
so
to
me,
smart
contracts
are
very
straightforward.
These
are
business
rules
right
and
in
different
systems.
We,
we
always
have
different
business
rules
that
govern
how
transactions
can
take
place,
but
really
what's
great
about
smart
contracts
is
the
way
that
the
different
parties
that
the
smart
contract
is
committed
to
the
blockchain.
B
So
everybody
knows
and
when
changes
are
made
to
it,
they
have
to
be
agreed
upon
and
and
again
there's
a
lot
of
transparency
and
visibility
to
that,
and
so
this
is
what
we
call
the
foundation
of
algorithmic
trust.
So
we
thought
that
was
very,
very
valuable.
Here's
a
look
at
what
we
did
in
our
smart
smart
contract.
B
B
Okay,
now
I'm
gonna
get
into
here
a
little
bit
about
oracle,
and
this
presentation
does
dig
in
quite
deep
on
oracle.
The
important
thing
to
recognize
is
that
it
didn't
necessarily
have
to
be
oracle,
or
there
are
components.
When
I
get
to
the
full
architecture,
there
are
components
that
can
be
swapped
out
and
not
necessarily
have
to
be
oracle.
B
In
this
case,
we
had
spoken
to
a
few
different
providers.
We
we
do
some
work
with
azure
g
actually
does
a
decent
amount
of
blockchain
work
with
azure.
We
talked
to
aws,
but
the
erps,
the
primary
erps
that
we
use
are
oracle
erps,
and
so
we
started
a
deep
conversation
with
them,
because
a
lot
of
our
financial
systems
are
oracle
and
what
I
really
liked
about
them
was
that
they
brought
a
complete
wing
to
wing
solution
to
the
table.
B
So
when
we
talked
about
it,
we
said:
okay,
fine,
we
have,
we
have
blockchain,
we
have
hyperledger
fabrics,
so
you
have
blockchain
as
a
service
great.
What
about
the
data
integration
and
they
say?
Oh
well,
we
have
our
oracle
integration
cloud
and
that
ties
directly
into
your
erps
and
into
the
blockchain.
Okay,
that's
a
that's
a
big
value,
ed
and
when
we
talked
about
the
rich
history
database
for
analytics
and
I'm
going
to
dig
into
all
of
that
a
little
bit
more.
B
So
I
want
to
kind
of
preface
this
with
saying:
yes,
there's
a
decent
amount
here
about
oracle,
because
that
was
our
implementation
partner,
the
vendor
of
choice.
We
also
worked
with
deloitte
as
our
consulting
partner,
but
again
that
you
know
this
is
a
hyperledger
meeting.
The
hyperledger
components
are
true
to
hyperledger
and
we'll
talk
about
where
oracle
adds
value
and
where
you
can
also
use
another
vendor.
B
So
the
key
kind
of
things
that
oracle
adds
out
of
the
box,
which
made
it
very
easy.
Is
you
know
it's?
It's
completely
a
blockchain
as
a
service,
so
it
runs
in
their
cloud.
They
do
offer
the
ability
to
install
it
in
your
own
data
center
kind
of
their
their
enterprise
blockchain
on
premise,
but
we
use
the
cloud
version.
They
set
up
all
the
rest
proxies
right
off
the
bat.
B
They
have
a
ledger
database
replaced
with
the
berkeley
database,
and
so
what
this
does
is,
instead
of
using
a
basic
the
main
database
that
comes
with
hyperledger.
The
berkeley
database
supports
sql
queries
as
well,
so
you
can
use
actual
sql
in
your
smart
contracts,
so
that
helps
a
little
bit
with
the
with
the
skill
set
for
your
smart
contract
developers.
B
They
don't
have
to
do
as
much
in
couch
database
language,
the
rich
history
database,
which
I'm
going
to
get
into
a
little
bit
more
on
some
other
slides,
because
this
was
a
huge
value.
Add
for
us
and
and
really
to
kind
of
give
you
the
the
20
000
foot
view
on
that
and
then
we'll
dig
in
a
little
deeper
is
what
they've
done
is
if
you
think
about
the
transactions
on
a
blockchain.
That's
a
transactional,
based
system.
B
So
now,
if
I
want
to
go
run
a
report,
those
queries
against
the
blockchain
are
expensive
in
terms
of
transaction
time
and
process,
especially
if
I
say
something
like
show
me,
the
last
12
months
of
activity
or
how
I
got
to
this
current
state
balance
right.
If
I
have
to
go
and
dig
through
the
blockchain
and
recursively
work,
my
way
back
to
come
up
with
those
numbers,
that's
going
to
be
very
poor
performance.
B
So
what
we
want
to
do
is
we
want
to
take
that
blockchain
data
and
move
it
into
a
data
warehouse
so
that
we
can
report
off
of
it
and
what
oracle
has
done?
Is
they
created
a
data
pump?
That's
built
directly
into
their
product
that
streams
the
data
in
real
time
into
an
autonomous
data
warehouse
in
the
oracle
cloud
and
then
from
there
we're
able
to
take
an
analytics
tool
like
oracle
analytics
or
you
could
swap
that
out
with
tableau
or
power
bi,
and
you
could
put
that
on
top
of
that
database.
B
To
then
do
your
reporting
and
originally
I
did
question
one
thing
I
questioned
about
that
was,
I
said,
you
know
the
big
value-add
with
the
blockchain
or
a
big
part
of
the
value-add
is
the
immutability
and
the
guarantee
that
the
data
can't
be
tampered
with.
Once
I
move
the
data
into
a
reporting
environment,
I
I
kind
of
diminish
that
a
little
bit
now,
that's
no
different
than
an
erp,
where
we
also
move
our
transactions
into
reporting
environments
and
potentially
they
can
be
changed.
B
But
I
was
very
adamant
about
the
fact
that
if
I
go
out
there
and
say
hey,
this
is
blockchain.
It's
completely
immutable
and
then
a
report
is
incorrect.
You
know
people
aren't
going
to
want
to
hear
the
the
technical
well
it's
technically
in
the
data
warehouse
anyway.
Oracle
has
since
solved
that
problem
with
blockchain
tables
in
their
database,
which
basically
do
hashing
of
the
previous
row.
So
it's
a
read-only
database
or
a
write-only
database
that
you
can't
make
changes
to
and
it
hashes
the
previous
row.
B
So
this
can
really
give
you
the
integrity
between
what's
on
the
chain
and
what's
in
the
reporting,
warehouse
and
then
security,
they
also
provide
the
security
with
their
identity,
management,
authentication
and
different
access
controllers
capabilities.
So
a
lot
of
this
we
could
do
ourselves.
I
could
go
out
to
hyperledger
site
and
download
the
code
and
I
could
start
spinning
up.
Docker
containers.
B
B
So
here's
the
total
architecture-
and
you
can
see
that
this
again
is
all
based
on
oracle
cloud
as
the
identity
management
analytics
cloud
where
we
do
the
dashboards
and
the
reporting
database
as
a
service.
The
autonomous
data
warehouse
which
gets
the
data
from
the
blockchain
stream
to
it,
there
is
the
actual
blockchain
platform
which
runs
hyperledger
fabric
and
and
but
on
the
oracle
cloud
and
pre
pre-built,
where
you
can
deploy
all
your
peer
organizations
and
smart
contracts,
everything
through
their
cloud
interface,
and
you
can
also
do
it
from
a
command
line.
B
They
do
have
command
line.
Rest
calls
that
you
can
deploy
things,
so
you
don't
have
to
use
the
ui
there's
the
integration
cloud,
which
is
how
we
connected
to
the
erps
we
tested
against
some
erps
that
were
running
in
a
cloud
sas,
others
that
were
on
premise.
We
also
tested
against
sap
and
we
kind
of
figured
out
how
to
do
all
that
we
did
data
validations
and
data
enrichment
and
we
created
a
front-end
app
okay,
so
there's
the
front-end
app
and
I'll.
B
Give
you
a
better
view
of
that
after
the
fact,
so
this
is
kind
of
how
we
looked
at
the
solution:
integration
with
the
different
products
right.
So
if
you
look
kind
of
on
the
right,
you
see
the
technology
stack
that
oracle
provides
right.
The
different
tools
and
on
the
left
is
kind
of
tied
back
to
that
capabilities
model
right.
How
do
we
go
ahead
and
look
at
those
different
capabilities
and
map
them
to
the
different
products?
And
this
is
a
case
where
again,
you
could
come
in
and
you
could
swap
something
out.
B
So
I
have
the
accounting
data
ingestion
and
the
enrichment
and
validation
and
the
exception
management.
That's
all
going
through
their
integration
cloud
product
and
in
that
integration
cloud
product.
They
have
a
tool
called
process
management
and
that's
how
we
set
up
the
dispute
management.
So
someone
could,
in
theory,
submit
a
transaction
that
meets
the
smart
contract.
It
goes
through.
It
comes
from
you
know
the
first
erp
it
goes
through
the
distributed
ledger.
B
It
validates
it
gets
posted
in
the
counterparty's
erp
and
then
it
automatically
gets
posted
back
the
the
conclusion
of
that
transaction
in
the
first
parties
erp
now
the
second
party
may
come
along
after
the
fact
and
go
actually
it
turns
out.
You
know
that
product
was
defective
right,
so
everything
met
the
rules
that
it
was
supposed
to.
But
now
I
want
to
dispute
it.
So
we
created
an
interface
through
the
web
ui
where
someone
could
go
in,
they
could
find
that
transaction
and
they
could
issue
a
dispute
on
it.
B
This
would
then
kind
of
shell
out
to
a
process,
management
workflow
and
it
would
change
the
status
on
the
blockchain
and,
and
the
great
thing
is
all
of
this
is
being
tracked.
So
anyone
who
goes
back
you
know
a
lot
of
times
when
we
hear
about
blockchain
use
cases,
and
you
hear
the
word
providence
right
and
we
hear
about
this,
especially
in
supply
chain
and
in
terms
of
responsible.
B
You
know
mining
practices
and
the
ability
to
kind
of
bring
things
into
the
supply
chain,
the
raw
materials
and
we
hear
about
the
provenance
right
and
that's
a
big
deal
to
me
as
a
financial
systems
professional
I
have
an
equally.
You
know.
I
have
an
equal
need
and
requirement
for
provenance
of
a
financial
transaction.
B
B
You
may
have
to
provide
a
number
of
forms
before
that
transaction
can
be
settled,
so
we
can
shell
out
by
knowing
some
of
the
data
that
we
get
in,
that
enrichment,
invalidation
step,
we
ping
our
master
data
system
and
we
could
find
out
information
about
the
legal
entities
that
are
participating
in
this
transaction
and
if
we
find
out
that
the
legal
entity
is
actually
in
a
jurisdiction
that
requires
different
paperwork.
We
can
hold
that
transaction
until
and
shell
it
out
to
this
workflow
and
wait
until
those
documents
are
collected.
B
Then
we
also
append
the
documents
into
the
transaction,
so
that
becomes
hash.
So
if
anyone
changes
the
documents
later,
you're
going
to
know
that
the
transactions
have
been
tampered
with
so
the
distributed
ledger
piece.
Obviously,
oracle
blockchain,
the
data
warehouse,
the
adw
analytics
and
again
any
of
these
pieces
could
be
swapped
out.
If
you
say
well,
you
know
I,
I
really
have
a
a
a
big.
You
know
a
looker
shop
right.
We
use
google
looker
for
analytics,
okay,
you
know
so
swap
that
piece
out
and
then
the
custom
ui
we
built.
B
So
looking
at
the
analytics
piece,
what
you
start
to
see
here
is
the
ability
to
take
that
blockchain
information
that
blockchain
data
and
turn
it
into
information
right,
and
so
you
can
start
to
see
different
things
here.
Total
number
of
invoices
invoices
amount
who
was
the
initiator
of
the
transaction
in
terms
of
different
businesses
and
other
key
metrics.
B
B
Nobody
wrote
that
okay,
that
is,
was
written
by
an
ai
engine,
that's
built
into
oracle,
analytics
cloud,
so
it
actually
looks
at
the
data
and
it
generates
a
natural
language
text
output
and
if
you
change
any
of
the
elements
on
the
report
or
if
you
filter
or
anything
that
executive
summary
will
automatically
update
based
on
the
data
that
is
now
available
in
the
view,
so
that's
very
powerful
and
something
that
we
really
liked
going
now
to
the
next
slide.
Here
I
talked
about
transactional
provenance
right.
B
So
here's
a
view
where
you
can
see
on
all
of
these
different
and
this
is
effectively
a
way
to
visualize
the
actual
blockchain.
So
when
we
talk
to
people
about
blockchain-
and
we
show
them
kind
of
these
different
steps
within
the
transaction
that
all
build
on
each
other
and
you
can
see
where
a
transaction
may
have
gone
into
a
hold
status,
you
can
see
how
long
it
was
in
a
hold
status
when
it
came
out
of
that
hold
status
and
why?
B
Why
did
the
status
quo
so
every
time
a
status
code
changes
you
effectively
get
another
entry
on
this
visualization,
and
this
is
pretty
much
near
real
time,
because
it's
streaming
directly
into
the
data
warehouse
which
is
then
presenting
itself
in
these
visualizations
so
out.
So,
throughout
our
closed
periods,
the
business
functional
users
can
go
in
if
you're
a
counterparty
you
can
go
in.
You
can
see
what's
holding
up
the
transaction
and
you're
able
to
really
kind
of
see
things
that
today
are
very
hard
to
dig
out
of
the
existing
system.
B
Okay,
so
this
is
just
kind
of
a
I
I
don't
have
a
demo.
I
do
have
a
demo,
but
I
wasn't
going
to
show
it
it
takes
too
long.
This
is
just
kind
of
a
gif
of
kind
of
the
user
going
through
the
front
and
just
to
kind
of
give
you
an
idea
of
what
the
ui
ultimately
looked
like
and
how
a
user
would
interact
with
the
data
and
be
able
to
go
in
and
and
kind
of
do
some
different
filtering
or
do
some
different
processing
execute
a
dispute.
B
Export
data
out
to
a
csv
file
is
what
you
just
saw
there.
So
this
this,
we
were
very
happy
with
this.
This
came
out
really
nice,
okay,
so
architecture.
Summary
ideal
solution
is
built
on
collection
of
pre-integrated
oracle
cloud
platform
services
right,
so
we
talked
about
all
those
different
pieces.
Another
thing
that
I'll
throw
in
a
couple
of
key
points
that
we
didn't
talk
about.
B
Why
else
is
blockchain
really
effective
for
this
solution
and
useful
one
of
the
things
is
built-in
resiliency
right
and
when
we
talk
about
the
way
a
peer-to-peer
network
operates.
Today
I
have
a
centralized
environment.
If
that
centralized
environment
goes
down,
everybody
is
on
hold
until
that
centralized
environment
comes
back
up
in
a
peer-to-peer
situation
where
I
have
multiple
participating
nodes
throughout
the
organization.
B
If
one
of
those
nodes
go
down,
the
other
nodes
continue
to
transact,
and
when
that
node
comes
back
up
it
catches
up
now.
In
this
use
case,
in
the
proof
of
concept,
we
only
used
oracle
right
right
before
the
pandemic
hit.
We
were
actually
in
the
process
of
spinning
up
peer
nodes
in
azure
to
connect
into
this
into
this
blockchain
and
become
part
of
this
consortium,
because
we
wanted
to
prove
that
we
could
go
cross
vendor
right.
That
wouldn't
be
as
much
of
an
issue
for
ge.
B
You
could
argue
that
maybe
one
of
my
business
units
would
say:
hey.
I
really
don't
want
to
use
oracle.
I
want
I
want
to
use
you
know,
aws
or
azure,
that's
less
likely
when
you're
dealing
in
an
intercompany
situation,
but
it
is
absolutely
a
requirement
if
you're
going
to
be
dealing
with
other
companies
right.
You
can't
go
out
to
you,
can't
be
in
health
care
services
and
go
out
to
all
the
hospitals
and
say
we
got
this
great
blockchain
solution.
B
We
want
you
all
to
use
it
by
the
way
you
all
have
to
use
oracle,
they're
they're
going
to
say
I'm
not
I'm
an
aws
shop,
I'm
an
ibm
shop,
I'm
azure!
I
I
I
don't
trust
any
of
this
cloud
stuff.
I
only
want
to
download
hyperledger
into
my
own
data
center.
You
know,
you're
going
gonna
have
to
deal
with
different
things.
B
So
hopefully
I'll
get
back
to
that.
At
some
point,
I
would
like
to
prove
out
that
I
can
connect
oracle
and
microsoft
and
prove
that
end
to
end,
but
that
resiliency
of
being
able
to
spread
it
across
multiple
clouds
across
multiple
nodes
is
definitely
a
big
big
piece
of
why
we
think
you
know
blockchain
could
be
a
good
solution
for
this,
and
you
know.
B
Ultimately,
we
think
that
we,
the
way
the
architecture
was
set
up,
we
would
be
able
to
expand
on
it
and
grow
it
and
build
it
out
to
like
I
said
earlier
on,
I
was
talking
about
maybe
introducing
ai
or
machine
learning
into
it.
So
I
think
that
you
would
be
able
to
get
some
of
those
additional
components
in
there,
because
we
did
kind
of
take
a
microservices
approach
to
it.
B
So,
for
the
most
part,
I'm
kind
of
wrapping
up
here-
and
I'm
done
with
this
part
and
we'll
be
able
to
go
into
some
q
and
a's
and
then,
of
course,
we're
going
to
hear
from
robert
and
then
we
can
do
some
more
q
and
a
at
the
end.
But
overall
I
will
leave
you
with
because
I'm
sure
it
would
come
up
as
a
question.
Where
are
we
now
right?
What
did
we
do,
and
so
basically,
where
we
are
at
the
moment,
is
we're
in
a
bit
of
a
hold
pattern.
B
We
proved
our
use
case
and
we
definitely
feel
that
we
proved
that
this
is
a
good
technology
and
and
cost-effective
too,
I'm
not
going
to
get
into
cost
and
talking
about
all
of
that
now,
but
it
was
much
more
cost
effective
than
I
thought
it
would
have
been
when
I
first
kind
of
dreamed
up
this
idea
and
and
said:
okay.
Well,
can
we
even
do
this
and
I
expected
it
to
be
more
than
it
was
from
a
cost
perspective
we
so
technology
wise.
B
So
when
I
talk
about
righted
inception
that
if
you
have
a
25
year
old
system
that
currently
does
not
enforce
that
things
perfectly
reconcile
on
submission,
okay,
that's
a
big
disruption
to
the
process
flow.
You
can
argue
it's
the
right
change
and
it's
one
that
we
have
to
make,
but
that
requires
the
business
the
functional
users
to
revamp
the
way
they
do
things
and
functional
doesn't
often
move
as
fast
as
technology
can
so
we're
kind
of
in
a
holding
pattern.
At
the
moment,
the
decision
was
made
to
go
with
option
three
for
this.
B
You
know
fiscal
year
is
to
re-platform
the
mainframe
in
the
cloud
on
an
emulator,
so
we
can
get
that
hardware
cost
out,
so
that
was
a
short-term
gain,
a
kind
of
a
quick
win
and
we
have
the
blockchain
solution
on
the
back
burner.
We're
hoping
as
we
go
into
21
that
we
would
pick
that
back
up
covet,
of
course,
has
disrupted
things
even
a
little
bit
further.
So
now,
I'm
a
little
unsure
of
when
exactly
will
be
the
right
time
to
pick
that
back
up.
B
But
ultimately
it's
going
to
be
decided
by
the
business
and
not
the
technology.
The
technology
is
what
it
is,
and
it's
not
that
hard
to
implement.
So
it's
really
about
the
business
having
to
recognize
what
does
it
mean
if
we
change
our
processes
and
what
are
we
going
to
have
to
do
to
accomplish
that?
So
I
think,
if
anything
that
was
one
of
the
big
lessons
learned.
B
Is
you
really
have
to
know
that
you
have
commitment
from
the
business
community
to
make
the
changes
that
are
going
to
need
to
be
made
to
take
advantage
of
this,
and
so
I'm
hopeful
and
and
optimistic
that
we
will
continue
down
this
road
and
we
can
apply
these
learnings
also
to
some
other
use.
Cases
that
we're
looking
at-
but
that's
where
we
are
at
the
moment
is
the
proof
of
concept
is,
is
just
that
it
was
a
successful
poc.
B
B
If
you
want
to
look
at
some
of
the
different
things
here
down
at
the
bottom,
I
have
a
blog
where
I
dive
deep
technically
into
it's
a
three-part
series
on
how
we
did
this
proof
of
concept
where
I
dive
in
very
deep
into
how
to
build
the
network
out
on
the
oracle
cloud.
How
to
do
the
integrations?
How
to
do
the
analytics
so
there's
a
lot
of
stuff
there
if
you're
interested
in
looking
at
it,
and
with
that
I'm
going
to
end
and
I'm
going
to
hand
it
over
to
robert.
C
Thanks
gary,
that
was
a
it
was
great.
We
do
have
a
couple
questions
here
in
the
chat
that
maybe
we
can
address
before
robert
goes
so
number
one.
I
know
you
mentioned
that
one
of
the
drivers
for
going
to
a
blockchain
based
solution
was
the
potential
cost
savings.
You
have
an
idea
about
the
expected
cost
savings
of
implementing
this
blockchain
based
intercompany
payment
solution
and
what
would
be
the
main
driver
of
those
costs?
Yeah.
B
Yeah,
so
this
is
a
little
bit
of
a
loaded
question.
That's
very
easy
for
me
to
answer
right
now,
because
I'm
coming
from
a
25
year
old,
mainframe
right,
I
had
nowhere
to
go
but
down.
I
could
have
pretty
much
implemented
anything
and
the
cost
would
have
gone
down
because
mainframes
are
unbelievably
expensive
and
so
no
matter
what
solution
we
picked,
we
would
save
money.
B
So,
like
I
said,
anything
is
going
to
be
less
than
mainframe
and
and
so
it
was
going
to
be
a
significant
cost
savings
and
I
felt
that
the
amount
that
we
were
going
to
be
looking
at
was
definitely
fair
and
anyone.
I
told
the
price
to
that
immediately
was
kind
of
off
the
table
like
they
like
they
were
like.
Oh
okay,
let's
talk
about
other
stuff,
then
like
it
was
kind
of
like.
If
that's
what
it's
going
to
cost,
then
then,
okay,
that's
good.
Let's
talk
about
other
things.
B
Okay,
so
that's
not
part
of
this
solution
right,
so
this
is
an
inter-company
solution,
so
it
doesn't
deal
with
the
suppliers
we
have
had
conversations
about.
Could
we
expand
this?
If
we
were
to
do
this,
could
we
then
expand
it
out
to
suppliers
and
the
first
kind
of
thought
there
was
well
okay.
Let's
talk
about
our
strategic
partners.
First
right,
maybe
we
could
bring
in
one
or
two
strategic
partners
put
them
on
the
blockchain.
We
also
thought
about
mergers
and
acquisitions.
That
blockchain
is
is
excellent.
B
A
distributed
ledger
is
excellent
technology
for
mergers
and
acquisitions
a
lot
of
times
when
you
spin
off
companies.
You
have
transition
service
agreements
right
tsas,
where
you
have
to
let
that
company
continue
to
operate
on
your
platform
for
a
period
of
time
as
they
migrate
off,
so
the
ability
to
kind
of
segregate
through
channels
and
and
kind
of
separate
the
way
the
work
is
is,
is
kind
of
co-mingled
and
have
that
security
built
in,
but
in
a
very
easy
way
to
segment.
B
C
A
B
B
B
B
D
E
C
A
So
looking
at
where
we've
kind
of
come
from
our
main
focus
has
been
traditionally
on
the
financial
services
and
telecommunications
sectors.
In
2007,
we
started
a
relationship
with
swift
where
we're
now
their
largest
global
services
partner,
we're
also
a
founding
member
of
the
linux
foundation's
hyperledger
project
and
our
strategic
partner
of
r3
digital
asset
and
vmware.
You
can
see
most
of
the
organizations
lined
up
here.
A
So
the
times
that
were
characterized
mostly
by
research
and
development,
some
proof
of
value
some
proof
of
concepts
experimenting
with
the
technology
really
kind
of
in
a
void
not
taking
into
account
any
of
the
non-functional
requirements,
but
really
looking
at
what
the
technologies
can
do
and
then
a
little
bit
more
about
about
the
un.
The
uncharted
waters
that
we've
treaded
at
the
start
there
following.
A
Some
of
the
devops
challenges
that
come
with
that,
how
there's
different
use
cases
and
different
approaches
connected
to
those
and
a
little
bit
about
the
it
infrastructure
as
well,
and
then.
Lastly,
I'll
talk
a
little
bit
about
our
catalyst
blockchain
platform,
which
is
our
as
chris
mentioned,
our
blockchain
platform
as
a
service
that
we
launched
earlier
this
year
in
the
summer.
A
A
We
did
a
kyc
data,
synchronization
and
consolidation
project
for
kvc
us,
and
then
we
also
did
a
central
bank,
digital
currency,
proof
of
concept
for
a
central
bank
and
a
stock
exchange.
So
really
this
this
period,
2016
2017,
was
really
characterized
by
getting
to
know
the
technology
really
going
into
the
code
figuring
out
how
it
works.
A
How
does
it
work
to
write
smart
contracts
in
go?
How
do
you
deploy
business
logic
in
a
decentralized
environment?
What
does
it
mean
to
have
a
public
blockchain
versus
a
private
blockchain
which
are
the
consensus
mechanisms
out
there?
These
were
all
kind
of
questions
that
we
started
tackling
and
then
looking
at
the
global
perspective
in
in
2016
2017,
you
can
see
here.
I
added
a
graph
from
google
trends
and
you
could
say
it
might
have
been
the
the
the
bitcoin
price
as
well,
but
it
isn't.
A
I
I
left
that
out
to
not
spark
any
frustration
or
discussion,
but
these
are
really
the
years
of
the
the
dlt
hype
train,
every
organization
that
had
heard
about
it
wanted
to
jump
on
the
hype
train.
It
was
the
year
of
the
crypto
bubble,
but
with
this
significant
amount
of
hype
also
comes
from
skepticism,
and
one
of
my
friends
who
works
at
a
financial
institution
here
in
belgium,
keep
saying
that
I
work
for
an
organization
that
promotes
the
solution.
A
Looking
for
a
problem,
I
I
bet
to
differ,
but
it's
it's
something
that
has
has
been
has
been
said,
a
lot
back
in
in
late
2016
and
2017
as
well.
So
I
mentioned
organizations
we're
really
focusing
on
experimenting
with
the
technology.
We're
looking
at
at
the
deep
technological
aspects,
for
example,
of
hyperledger
fabric,
and
not
so
much
about
all
the
different
non-functional
requirements.
A
It
was
back
in
that
day
or
that
year
that
the
focus
was
really
technology
driven
and
not
as
much
business
or
use
case
driven,
which
led
to
to
some
misalignment
between
the
business
area
and
their
expectations
versus
the
technology
itself,
which
then
in
turn
led
to
quite
slow
adoption
because,
of
course
distributed
ledger
technology
often
built
on
on
a
consortium
of
organizations,
and
so,
if
there's
some
misalignment
between
business
expectations
and
technology.
Of
course,
your
consortium
building
is
on
a
very,
very
slow
base.
A
What
happened
there
for
intellect
to
you?
This
was
2018.
Our
team
grew
from
around
10
to
to
around
25
people
strong.
We
were
focusing
mostly
on
hyper
electric
fabric,
1.0
and
1.4
on
corda.
We
continued
some
some
some
research
and
development,
and
then,
of
course,
we
started
looking
into
the
digital
asset
modeling
language
as
well.
A
Now,
something
that
was
quite
important
from
our
perspective,
really
in
in
these
years,
was
the
the
increased
adoption
of
virtualization
and
containerization,
which
were
really
crucial
in
the
the
further
adoption
of
blockchain
technology
itself.
As
I
mentioned
in
that
first
phase,
we
that
it
was
really
characterized
by
technology
focused
where,
in
those
years
organizations
really
realized.
Okay,
they
started
learning
about
the
technology.
Now
we're
looking
at
the
businesses
now
we're
looking
at
the
use
cases.
How
can
we
actually
leverage
this
technology
and
which
use
cases
make
sense
to
leverage
dlt?
A
So
with
potential
clients.
We
did
a
lot
of
workshops
with
a
lot
of
trainings,
really
teaching
these
organizations
what
dlt
could
do
and
which
are
some
of
the
use
cases
that
dlt
could
be
leveraged
for
and
which
use
cases
you
didn't
want
to
use
distributed,
ledger
technology
for
so
this
is
the
year
where
we
really
shifted
from
being
a
traditional
technology
organization
to
really
tackling
those
those
different
methodologies.
A
A
That's
a
stand-alone
application,
you're,
building
an
application
that
has
to
be
integrated
with
legacy
systems
that
has
to
be
scalable
towards
the
future
that
has
to
become
deliver
a
competitive
pricing
versus
the
the
com,
the
competing
solutions
that
you
might
want
to
put
in
place.
As
per
gary's
comments,
you,
you
were
working
with
a
mainframe.
A
Of
course
the
only
way
is
down
in
terms
of
costs,
and
these
are
the
things
that
we're
looking
at
in
these.
In
these
years,
you
can
see
that
there
was
collaboration
at
the
center
of
building
solutions
like
these,
and
I
think
this
is
a
perfect
segway
to
give
a
a
little
shout
out
to
the
hyperledger
community,
where
the
the
community
that
we've
that
you've
built
and
the
ecosystem
around
that
have
really
been
the
cornerstone
of
blockchain
adoption,
especially
for
hyperledger
greenhouse
products.
A
Some
of
the
other
trends
that
we've
seen
in
the
last
few
years,
especially
now
with
the
pandemic,
is
the
central
bank,
digital
currency,
hype
or
trend.
I
should
call
it
we've
seen
a
lot
of
of
collaboration
between
public
private
sector,
on
a
variety
of
proof
of
concepts,
research
projects,
working
groups
and
actual
project
implementations
as
well
and
now.
Lastly,
we've
also
seen
some
some
new
marketplaces
in
the
financial
industry
focused
on
insurance,
reinsurance
and
really
combining
that
with
distributed,
ledger
technology
and
and
multi-party
smart
contracts.
A
Looking
at
some
of
the
projects
that
we
have
built
in
the
last
few
years
and
really
comparing
them
so
we've
we've
come
to
the
conclusion
that
the
use
case
often
dictates
the
approach
you
want
to
take
to
building
a
a
dlt
application
or
a
solution.
I've
highlighted
two
two
of
the
solutions
that
we've
built
for
clients
here
today.
A
So
obviously,
digital
vouchers
versus
physical
vouchers
in
today's
day
and
age
with
the
global
pandemic
is
100
the
preferred
choice,
and
then
you
of
course,
have
the
use
case
of
being
able
to
support
your
local
economy
in
in
times
where
it's
well
needed
as
well.
So
this
has
been
a
project.
We've
we've
done
the
end-to-end
development
for
in.
I
think
it
was
less
than
half
a
year,
seeing
how
there
are
still
clients
being
onboarded.
A
Today,
I
think,
a
couple
weeks
ago,
the
I'm
living
in
in
belgium
here
and
a
couple
weeks
ago,
the
the
local
region
of
bologna.
I
was
on
board
as
a
client
to
the
platform
and
they
committed
over
1.6
million
euros
to
be
to
be
spent
on
on
in
vouchers.
So
that's
great
to
see
that
there
are
still
clients
being
on
board
and,
if
we're,
comparing
this
to
to
a
widely
different
use
case,
a
widely
different
project
that
we're
working
on
today,
which
is
cube.
A
A
And
let
me
tell
you
that
comes
with
its
own
set
of
challenges,
there's
a
lot
of
compliance
that
we
have
to
take
into
account
and
existing
flows
at
each
of
the
bank.
Sides,
which
has
required
us
to
take
a
a
completely
different
approach
and
we're
releasing.
Or
we
have
released
a
v1
of
this
earlier
this
year
and
we've
also
done
the
end-to-end
development
there.
So,
looking
at
the
use
case
and
how
each
use
case
kind
of
dictates,
a
different
approach
is
something
we've
noticed
as
well.
A
We
started
with
some
of
the
challenges
so,
as
our
developers
have
been
building
blockchain
applications
for
the
last
few
years
now
they
always
ran
into
some
of
the
same
challenges
they
had
so
setting
up
a
blockchain
network.
Gary
you
mentioned
you,
you
managed
to
set
up
a
simple
blockchain
network
in
15
20
minutes.
A
That's
something
that
a
few
years
ago
was
unheard
of,
and
traditionally
that
is
a
very
lengthy
and
manual
process
includes
a
lot
of
manual
scripting
and
a
high
level
of
expertise.
While
today
there
are
solutions
and
and
gala's
blockchain
platform
is
one
of
them
where
that
is.
That
is
no
longer
the
case.
Another
challenge
maintenance.
Okay,
so
now
you've
set
up
your
network.
You've
set
up
your
you've
got
your
application
running
now.
A
You
need
to
maintain
everything
so
maintaining
that
that
uptime
of
the
network
requires
a
high
amount
of
time
or
used
to
require
a
high
amount
of
time
and
resources
from
the
devops
teams
and
again
is
characterized
by
a
lot
of
manual,
scripting
reactive
processes
and
then,
lastly,
the
the
management
itself
of
your
network
and
your
organizations
and
your
network
still
oftentimes.
This
happens
in
in
sort
of
a
centralized
way
with
a
network
operator
or
network
administrator,
and
then
there's
few
options
available
for
for
this
to
to
be
done
on
chain
fully
decentralized.
A
So,
looking
at
the
main
features
and
how
these
features
tackle
some
of
the
hurdles
that
that
we've
come
that
we've
come
about
in
the
last
few
years
that
unified
management
and
operations
console
that
abstracts
away,
that
those
highly
technical
aspects
right,
you,
you
don't
have
to
manually
script
anymore,
to
set
up
a
new
node
or
to
add
an
organization
to
a
specific
channel
or
to
upload
your
chain
code.
This
is
all
possible
just
in
a
few
clicks
through
the
interface
so
again
less
a
lot
less
time
necessary
to
perform
these
actions.
A
A
And
so
we've
we've
made
that
possible
and
then,
similarly,
also
with
the
deployment
in
multiple
availability
zones
and
over
multiple
clusters
for
increased
reliability,
then
security
we
have
our
hsm
supported
as
well
as
ashikorp,
vault
and
kubernetes
secrets
to
control
your
security,
materials
and
digital
identities,
user
management,
pretty
straightforward
monitoring
and
alerting
dashboards.
So
here
we've
created
a
set:
we've
created
a
dashboard
where
you
can
manually
conf,
where
you
can
configure
your
monitoring
and
alerting
there's
failover
mechanisms.
I
mentioned
that
earlier
and
as
well.
A
There's
a
possibility
to
integrate
the
system
with
your
existing
monitoring
tools
as
well,
and
then,
lastly,
are
entergrise
great
support.
So
I
think
hyperledger
fabric
has
is
this
great
framework
that
allows
you
to
build
your
blockchain
networks
and
we've
taken
that
and
really
built
around
that
an
enter
enterprise,
great
system,
including
the
support,
so
that
you
can
reduce
your
operational
expenses
having
to
look
for
these
highly
technical
profiles
to
support
your
your
network,
your
applications
that
you
might
have
running.
A
So
some
of
the
some
of
the
screens
I
added
some
screens
of
of
our
product
to
just
give
you
a
bit
of
a
an
idea
of
what
it
looks
like.
So,
on
the
left
hand
side
you
can
see.
This
is
from
the
perspective
of
one
organization
in
this.
In
this
example,
it's
called
bank
one.
You
can
see
on
the
left
hand
side
in
the
top
there's
the
dashboard,
with
the
go
metrics
ledger,
metrics,
all
all
metrics-
that
you
require
and
also
events
and
logging
is
available
there.
A
A
A
If,
if
you
want
to
access
your
your
orderers
details,
then,
secondly,
there's
the
the
peers
here,
where
we've
developed
the
functionality
of
being
able
to
to
create
your
roads,
your
own
peer
sets,
which
are
template
configurations
for
for
your
peer
nodes.
You
can
see
here
all
the
actions
that
you
can
perform
related
to
your
peers,
so
you
can
remove
it.
You
can
join
it
to
a
channel.
You
can.
You
can
install
chain
code,
you
can
see
at
the
bottom
the
channels
that
your
peer
is
connected
to
on
the
left.
On
the
right
hand,
side.
A
A
You
can
see
the
policy
so
for
this
the
policy
is
all
meaning
that
all
the
existing
organizations
that
are
part
of
the
channel
have
to
vote
yes
to
the
proposal
in
order
for
that
new
organization
to
be
added
to
the
channel
as
for
example,
so
that's
about
it
from
my
side.
Thank
everyone.
I'm
looking
forward
to
any
questions.
If
you'd
like
any
more
information,
please
don't
hesitate
to
reach
out
from
to
me,
and
I
guess
I
guess
chris,
we
can
jump
into
the
qa.
C
Yeah,
thank
you,
robert.
That
was
that
was
great
and
thanks
again
gary
for
for
your
insights
as
well.
So
we
have
one
question
in
the
chat
right
now
from
wilshankar
mushanka.
I
don't
know
if
you
want
to
just.
If
I
want
to
unmute
you
right
now,
and
you
can
ask
it
yourself,
as
we
have
gary
and
robert
here
see,
if
I
can.
D
D
You
have
shown
us
the
architect
that
blockchain
enterprise
solution
so
blockchain
is
they
see
only
the
part
of
the
solution
I
mean
it
means
mostly.
People
say
that
it's
blockchain
is
only
ten
percent
of
the
solution
and
if
we,
if
we
say
that
I
mean
if
we
show
the
some
guy
who's
me,
actually
people
are
still
confused
with
the
blockchain
they
they
are
still
denying
mode.
D
And
now
now
things
are
changing
bit
but
still,
and
they
say
that
if
you
say
that
there
is
no
intermediary,
then
if
only
10
persons
are
in
on
the
blockchain
still
you
are
using
the
centralized
system,
so
you
can
say
that
bitcoins
are
other
cryptocurrencies
are
no
intermediary,
but
these
type
of
solution.
We
can't
say
no
intermediary
and
other
things.
I
would
say
they
say
that
blockchain
is
not
a
is
a
part,
is
a
feature
we
can
use
rather
than
we
can
say
the
blockchain
solution.
So
yeah,
thank
you.
B
Sure
sure
absolutely
so,
so
I
I
think
you're
spot
on
in
in
what
you're
saying,
in
terms
of
it
being
a
part
of
the
solution
in
terms
of
an
enterprise
architecture
right
and
I
was
very
clear
to
our
functional
users.
You
know
we
have
erp
systems,
we're
not
replacing
the
erp
and
we
and
we
were
very
much
adamant
about
the
fact
that
the
use
the
right
tool
for
for
what
your
needs
are,
and
so
we
have
these
complicated
enterprise,
resource
and
planning
systems.
B
General
ledgers,
with
all
these
rules
and
processes
built
in
we
weren't
looking
to
change
any
of
that,
and
that's
still
the
source
of
record
for
the
particular
entity.
But
what
we
wanted
to
do
was
be
able
to
extend
that
ledger
to
be
able
to
interact
better
with
other
ledgers
using
you
know
a
dlt,
so
I
do
think
it
is
just
a
piece
of
the
solution.
B
It
is
certainly
not
meant
to
replace
those
solutions,
but
if
you
think
about
today,
I
run
a
report
and
then
I
take
that
csv
file
and
I
ftp
sftp
it
over
to
the
other
party
for
them
to
upload
into
their
system.
Those
are
the
kind
of
transactional
changes
that
we're
trying
to
improve
upon
and
say
we
can
do
this
better
in
a
more
transparent
way,
and
you
know
as
far
as
the
intermediaries.
B
You
know
we
definitely
struggled
in
some
of
our
brainstorming
sessions
around
how
how
phyllis
you
know
the
blockchain
philosophy
and
what
it
means
to
be
decentralized
and
we
started
going
down
a
rabbit
hole
where
we
were
like.
Well,
we
created
a
ui.
Technically
that's
a
centralized
component,
because
if
the
ui
goes
down,
then
it
doesn't
matter
that
your
data
tier
that
the
blockchain
is
on
is
distributed
because
the
ui
is
down.
So
then
we
started
to
extrapolate
on
that.
B
So
you
do
have
to
come
to
a
point
where
you
say:
what's
decentralized
and
what
am
I
willing
to
accept
as
being
a
common
use
layer
in
the
solution
and-
and
I
think
for
everybody-
that's
going
to
be
different
depending
on
their
their
circumstances,
and-
and
so
you
know
the
last
part
I'll
leave
off
with
with
that.
Is
that
one
of
the
other
things.
D
C
B
Sorry
about
that
I
seem
to
have
a
little
bit
of
a
problem.
I
think
a
wire
gut
got
moved
and
and
all
of
a
sudden
things
drop
so
I'll
I'll
wrap
up
there,
but
yeah
again
telling
people
about
blockchain,
blockchain
blockchain
actually
became
a
detriment
to
our
project,
because
it
just
became
this
focal
point
of
this
new
technology
that
maybe
people
didn't
fully
understand.
They've
heard
some
things
about
bitcoin,
maybe
they're
a
little
nervous
and
and
so
again
I
mean
it's
really
just
a
different
piece
of
a
data
tier
for
transactional.
A
What
it
does
do,
though,
is
that
it
introduces
a
whole
set
of
new
possible
business
models,
new
possible
governance
models
and-
and
just
as
you
mentioned
gary
it
introduced
for
for
for
ge,
it
introduced
a
new
set
of
working
with
the
with
invoices,
or
at
least
adding
your
your
the
information
right
from
inception,
which
in
fact
it's
just
a
new
process.
It's
it's
a
process
change,
so
I
think
yes,
blockchain
does
introduce
a
whole
set
of
new
possibilities
through
business
models
through
through
governance
models.
C
D
D
So
I
don't
know
if
you
understand
it
that
the
authentication
piece
where
there
can
be
fraud
is
only
on
dlt,
so
we
developed
it
and
I
think,
if
I'm
not
mistaken,
it
was
hyper,
ledger,
0.9
or
something
pretty
early.
So,
but
because
of
our
funding
and
all
we
stop
that
project,
it's
already
done
and
we
want
to
improve
upon
it.
D
D
I
mean
it
was
efficient
like
when
the
people
used
to
open
their
android
apps
or
the
iphone
apps.
It
used
to
open,
speak
with
the
dlt
and
say:
okay,
because
our
we
use
the
uuid
of
the
phone
and
certain
other
abstracts
of
the
phone
to
build
your
stuff.
The
encryption
and
it
was
stored
on
the
phone
itself
and
an
entry
equivalent
was
in
beginning.
B
It's
certainly
an
interesting
use
case.
You
know,
I'm
I'm
not
gonna
pontificate
on
things
that
I
don't
know
about.
You're,
definitely
getting
out
of
my
area
of
expertise
when
it
comes
to
that,
but
I
I
think
you
know
the
idea
that
this
technology
can
be
applied
to
rethink
a
lot
of
different
problems
is
valid.
B
I
do
think
you
know.
I
think
robert
mentioned
it
earlier.
You
know
we
we
were
kind
of
told
at
times
you
know
don't
go
looking
for
just
because
you
have
a
solution,
be
careful
going
to
look
for
problems
to
fit
that
solution.
So
I
I
think
you
have
to
examine
that
closely
to
see.
If
it's
are,
is
it
better
than
what's
available
today?
How
does
it
improve
upon?
What
is
the
industry
standards
today
and
if
you
think,
you
really
got
something
there,
that's
either
more
more
secure
or
more
cost
effective,
more
performant.
B
D
B
D
Because
the
authentication
hash,
so
we
used
it
for
that,
but
it
was
interesting,
I
being
an
infrastructure
person
and
not
into
the
coding
piece.
We
developed
a
ten
person
team,
I
explained
them,
they
went
and
learned
the
hyper,
the
edger
first
and
then
they
built
upon
it.
So
was
interesting
that
at
least
we
could
bring
something
from
a
drawing
out
of
there.
D
C
Thank
you
both
to
gary
and
robert
and
we're
always
encouraging
more
people
to
pitch
in
ideas
as
to
what
they'd
want
to
see
presented
at
future
meetups
or
if
you
want
to
present,
please
feel
free
to
reach
out
to
myself
and
in
the
meantime,
if
you've,
any
more
questions
for
gary
or
robert,
I
included
both
their
information
in
the
meetup
link
and
again,
thank
you
all
for
attending
and
again,
thank
you
to
our
presenters
as
well.
Chris.
B
A
Looking
forward
to
have
more
appreciate
it
chris
and
thank
you
as
well
gary
for
the
interesting,
the
interesting
presentation
and
maybe
one
question
to
agree
to
the
audience.
Something
that
I'd
like
to
know
is.
Are
there
any
hurdles
that
you
haven't
heard
today
from
from
either
gary
or
myself
that
you
have
experienced
that
you
have
had
the
challenge
and
pleasure
of
tackling?
If
so,
I'd
love
to
hear
about
those
as
well
from
anyone
in
the.
D
Tps
the
number
of
transactions
like
kerry,
says
they
have
many
applications.
There
are
number
of
transactions
there.
So
I
want
to
know
me.
I
passed
my
question
so
I
said
I
already
asked
a
big
question
so
whether
to
write
it
anyways
how
how
about
the
tps
about
means?
Actually
we
always
face
the
problem
in
enterprise.
A
Solution,
yeah,
I
think
dps
or
maybe
just
scalability,
is,
is
definitely
an
interesting
question
and,
depending
on
on
the
the
dlt,
you
use
it's
it's.
It's
gonna
be
a
different
answer.
So
I'm
not
sure
if
you
were
talking
about
a
specific
technology,
but
definitely
an
interesting
and
interesting
question
and
and.
D
D
And
suppose
there
is
a
erp
solutions
is
already
working
and
it
is,
there
is
a
lot
of
transactions
are
going
on
and
while
and
adding
as
a
blockchain
as
a
means
of
some
part
in
the
blockchain.
Definitely
we
have
to
compromise
some
speeds
or
some
way
to
in
a
way
that
it
should
manage,
but
whatever
the
transactions
were
going
on
previously
before
the
blockchain.
A
Yeah,
I
think
that
comes
back
again
to
what
gary
said
earlier.
If
you
have
a
solution,
but
the
alternatives
are
better
than
looking
into
yeah.
That's
definitely
one
of
the
challenges
exactly
blockchain
might
offer
solutions
on
some
perspectives,
but
then
there
might
be
other
perspectives
that
that
that
it
doesn't
and
that
other
other
technologies
might
perform
better
at
and
then
I
think
exactly
it's
the
it's,
the
balance
you
have
to
find.
C
E
Yeah
I
mean
we're
we're
putting
together
a
an
offshore
exchange
and
we
have
an
organization,
banking
organizations.
They'll
hold
the
fx,
we
have
custodians,
they'll
hold
the
crypto
and
where
he
acts
as
a
media
in
between,
and
we
we
stated
that
very
clearly
and
when
you
deal
with
other
countries
or
or
organizat,
I
shouldn't
say
countries.
When
you
deal
with
private
organizations,
they
tend
to
understand
that
you're,
not
you're,
not
a
risk
you're,
not
putting
your
clients
at
risk,
you're
dealing
with
accredited
organizations
that
hold
the
value
and
the
assets.
E
The
weight
of
that
is
an
order
magnitude
above
the
weight
of
just
being
a
company,
and
I
find
that
problematic,
but
they
also
ask
about
the
technology.
So
I
was
wondering
if
there's
some
way,
that
the
technology
can
be
expressed
and
clearly
show
that
we
are
not
what
they
fear
or
I
should
say
we're
not.
I
mean
they
should
fear
the
crypto
markets
for
a
very
for
a
variety
of
reasons,
but
not
what
we're
trying
to
start
yeah.
So
I
was
wondering
if
this.
B
Definitely
yeah
definitely
avoid.
You
know,
I
think
dlt,
you
know
if
you
and
we
started
even
using
that
internally,
I
told
you
know
people
on
the
team
stop
saying
blockchain
say
distributed,
ledger
right
and
and
so
you
know
that
kind
of
changed
the
conversation
a
little
bit.
I
would
definitely
remove
the
terms
crypto
and
blockchain
from
your
discussions
with
them.
I
think
you
know
and
because
you
really
are
you're
talking
about
a
distributed
ledger.
You
know
all
blockchains
are
distributed,
ledgers,
not
all
distributed
ledgers
or
blockchains
right.
B
So
in
theory,
you
could
potentially
do
a
distributed
ledger
on
a
non-blockchain
solution
and
and
go
and
have
that
conversation.
So
I
think
hyperledger
you
know
hyperledger
is
not
a
cryptocurrency.
So
if
you're
on
hyper
ledger,
you
could
definitely
kind
of
sell
that
but
try
to
avoid
even
going
down
that
rabbit
hole
by
not
really
focusing
on
or
emphasizing
blockchain
or
crypto.
As
part
of
your
solution.
E
Yeah
that
I
I
definitely
agree
in
terms
of
what
we
write
up.
We
should
alter
it
as
you're
saying,
but
they
still
want
the
technology
and
I'm
trying
to
find
a
way
of
demonstrating
on
a
platform
that
the
business
rules
preclude
us
from
being
part
of
the
risk
profile,
because
they
are
obviously
very
risk-averse.
I
I
was
wondering
if
there's
a
platform
approach
that
could
make
that
easier
to
understand
to
semi-technical
leadership
within
these
organizations
got
you.
A
Yeah
just
a
few
thoughts
from
my
side
on
that
joe,
I
think
there,
your
challenge
that
you're
dealing
with
is
also
part
of
the
the
the
challenge,
the
broader
challenge.
That
is,
the
fact
that
regulations
and
legal
framework
extend
to
lag
behind
innovations
and
and
technical
innovations
there.
So
I
think-
and
we've
seen
this
in
this
throughout
the
history
many
times.
I
think
what
we're
dealing
with
right
now
is
exactly
that
regulations,
legal
frameworks,
certain
thought,
processes
of
organizations
and
even
people
lag
behind
the
actual
innovation
there
that
we
have
today
with
distributed
electric
technology.