►
From YouTube: Hyperledger Madrid hosts "Hyperledger Cactus: Un framework de integración para plataformas DLT"
Description
Hyperledger Cactus tiene como objetivo proporcionar una integración descentralizada, segura y adaptable entre las redes de cadenas de bloques.
A medida que la tecnología de las cadenas de bloques siga evolucionando, la integración de las cadenas de bloques se convertirá en un tema cada vez más importante en el ecosistema más amplio de las cadenas de bloques.
Este framework incluye un conjunto de bibliotecas, modelos de datos y SDK para acelerar el desarrollo de una aplicación de servicios integrados.
El objetivo de Hyperledger Cactus es crear un sistema que permita a los usuarios realizar transacciones seguras entre todas las cadenas de bloques más utilizadas.
https://www.meetup.com/Hyperledger-Madrid/events/274820248/
----
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
B
Thank
you
very
much
for
your
time
for
attending.
Today
we
have
with
us
enrique
alcázar.
He
works
as
a
technical
architect
at
accenture,
and
he
also
works
on
several
suit
projects,
but
specifically
law.
One
of
them
is
hyper
layer,
cactus
and
well.
He
is
a
person
who
has
been
in
the
world
of
the
block
change
since
2012,
so
he
is
going
to
share
with
us
today
part
of
his
knowledge.
So
all
yours,
enrique.
C
Thank
you
very
much
handyman
delighted
to
meet
everyone
and
come
to
talk
to
you
about
tgp,
the
cacti
so
call
to
the
center
of
the
cemetery.
So
I
can
jump.
It
is
a
small
space
to
tell
you
that
what
I
am
going
to
tell
you
is
not
mine
and
you
have
to
have
what
to
really
thank
is
peter
as
yibari
who
is
a
fellow
accenture
who
is
the
designer
and
creator
of
the
hyper
layer
cactus.
So
then
later
we
will
see
him.
C
We
will
be
able
to
play
at
the
end
and
we
will
see
how
we
can
contact
the
queue
you
are
not
chasing
all
of
them,
but
if
you
are
interested
to
continue
advancing
with
it,
ok
then
'the
league'
to
start
and
this
to
cover
our
backs
for
everyone
who
wants
to
use
it
now.
The
project
is
still
in
the
incubation
phase.
C
It
is
not
ready
for
extras
in
production.
The
release
1.0
is
not
ready,
yet
it
is
on
the
roadmap
in
January.
They
are
going
to
be
the
final
ticos.
We
are
going
to
see
the
whole
presentation
at
the
end,
but
right
now,
if
you
take
a
cactus,
we
really
want
it
to
take
it.
So
we
start
playing.
It
is
for
learning
to
use
the
technology
start
developing
with
it
and
will
start
to
introduce
the
best
concept
jobs,
but
it
is
not
ready
to
be
used
in
productive
environments.
S.
C
We
do
not
start
by
telling
what
is
the
gp
read.
Cactus
is
basically
a
walk
framework
plan
that
is
designed
for
the
business
environment
to
carry
out
transactions
within
multiples
within
and
between
multiples
of
letes,
instead
of
being
a
ltd
delete
is
that
it
is
how
they
have
tried
make
other
or
similar
brooches.
This
in
the
world
of
blogs
is
purely
open.
It
was
introduced
being
to
introduce
an
sdk.
It
says
the
case
and
why
this
has
been
done
good
because
mainly
to
solve
the
problem
of
fragmentation
between
blogs
and
letes.
C
And
now
we
will
see
why,
specifically,
if
tomorrow,
it
is
start
using
another
tele
subject
in
the
system.
Other
letters
in
the
system-
you
don't
have
to
make
any
changes
to
the
system
infrastructure
so
that
you
can
speak
with
a
new
reflection
because
everything
is
already
inside
the
scoop.
Well,
let's
talk
about.
How
is
the
fragmentation
that
We
have
commented
on
this
before,,
which
is
a
problem,,
but
to
try
to
see
the
size
of
the
problem?
C
More
clearly,,
basically
to
try
to
have
n
numbers
of
lakers
connected
in
networks
with
ce
numbers,,
to
connect
them
all
to
each
other,,
making
a
complete
graph
of
connecting
them
to
each
other
for
each
new
node,
but
not
for
each
new
node
for
each
new
leger
that
we
are
introducing
grows
quadratic
men,
the
number
of
connections
that
would
have
to
be
made
between
the
lakers
to
ensure
that
the
transactions
are
verified.
We
can
verify
the
transactions
in
all
or
we
can
read
from
any
to
write
to
any
cetera
right
now.
C
There
are
already
thousands
of
lakers
in
the
world
thousands
of
different
networks
in
with
different
technologies
that
are
operating,
but
if
we
only
wanted
to
connect
100
laws
or
have
the
ability
to
have
an
application
that
consumes
data
from
100
lakers,
we
would
be
talking
about
doing
5000
individual
integrations
with
current
systems.
The
advantage
of
using
cactus
is
that
this
whole
process
is
automate
now,
and
this
is
what
cactus
is
and
because
it
has
been
done
now.
C
We
have
specifically
talked
about
the
position
that
cactus
finds
within
the
hyper
leader
green
house,
because
they
are
gp
learning
in
which
pearl
yesterday
we
have,
on
the
one
hand
the
delights.
That
is
what
is
most
often
paid
attention
to,
on
the
other
hand,.
We
do
not
have
the
bookstores
that
they
are
tremendously
useful.
We
have,
on
the
other
hand,
the
tools
and
then
the
laboratories
and
some
that
are
specific
for
different
components,
because
cactus
is
located
within
tools
and
arguments
to
place
it
within
giant
libraries
than
these
arguments.
C
But
right
now
it
is
located
within
tools
in
case
of
more
generic
use,
for
cactus
is
when,
in
our
business
case,
we
need
multiple
test
laws
to
interact
with
each
other.
For
example,
when
our
application
is
adding
value
or
generating
value
when
different
data
or
assets
that
are
in
different
laws
have
to
work
together.
For
example,,
if
we
have
a
leger
that
is
responsible
for
registering
transactions
and
a
leger
that
is
responsible
for
verifying
identities,.
C
We
are
going
to
see
first,
the
four
keys
are
that
absolutely
everything
and
this
we
will
see
later
also
that
absolutely
everything
is
based
on
plugins.
It
is
done
to
maximize
flexibility.
It
is
future
proof
to
be
able
to
add
new
new
laws
in
a
relatively
simple
way
that
it
is
secure
by
default,
avoid
that
developers
have
to
do
anything
to
that
it
be
a
deployment
that
is
secure
and
consistent
type
passwords
by
default
type.
C
That
requires
explicit
permissions
from
the
developers,
know
an
integration,
etcetera
that
seattle
free,
which
basically
means
that
users
do
not
have
to
pay
any
type
of
token
any
type
of
asset
to
carry
out
operations
and
that
operators
do
not
have
to
charge
for
performing
ar
or
to
verify
the
transactions
that
is
totally
English.
It
can
be
possible
to
implement
a
system
to
charge,
but
it
is
designed
so
that
it
is
so
that
you
neither
have
to
pay
to
use
cactus.
C
We
are
aiming
not
to
have
it
and
the
10
most
relevant
protocols
of
td-lte,
but
to
have
them
all
to
have
29
percent
of
the
existing
protocols
that
are
compatible
with
this
network,
and
we
believe
that
it
is
unasurable
that
it
is
possible
thanks
to
the
plugin
system
that
is
developed.
We
also
want
to
prevent
double
spending
between
lakers
as
long
as
it
is
applicable,
eviden
Obviously,,
if
one
of
the
laws
cannot
guarantee
finality,.
This
is
not
a
possibility,,
but
for
the
others
and
what
controls
to
avoid
it,.
C
We
want
to
preserve
the
characteristics
of
the
particular
laws,
and
we
want
to
have
the
opportunity
to
scale
the
solution
horizontally.
.,
because
blog
chains,
as
we
surely
know,
is
that
they
can't
scale
horizontally
or
scale
painfully
horizontally.
The
vast
majority
add
a
new
node
to
the
network.
All
it
does
is
make
the
network
even
slower.
They
can
scale
vertically,
but
not
horizontally.
The
idea
of
cactus
is
that,
since
it
can
scale
horizontally,
it
will
never
be
the
nec
boat.
It
will
be
the
solution
to
the
scalability
problems.
How
are
we
going
to
see
now?
C
Well,
the
getting
a
little
closer
to
the
fire,
the
architecture
of
cactus.
This
is
what
it
looks
like.
We
can
see
bottom
right,
two
networks
in
this
example
a
say
network
and
a
public
and
a
quorum
network,
p
rivada,
in
which
the
two
are
interacting
with
the
web
application.
The
important
thing
to
see
here
at
the
moment
is
that
we
have
a
plugin
that
is,
for
each
of
the
two
laws.
C
C
Art
agreed,
we
have
the
routing
interface,
which
at
the
moment
is
literally
just
a
script
interface.
It
is
planned
to
evolve
it
in
the
pipeline
jr.
We
will
see
what
it
is
not
going
to
change
with,
and
finally,
we
have
the
business
logic
plugin.
That
is,
that
is
designed.
The
components
with
which
it
interacts
is
designed
to
act
and
to
behave
in
a
plugin
manner.
C
In
terms
of
the
architecture
that
you
mentioned
before,
the
code
is
written
in
taiz
script
and
it
is
possible
to
make
a
bandel
with
web
for
what
we
use
now
and
modern
as
to
have
a
repository
gigantic,
where
we
have
all
the
packages
of
all
the
plugins
included,
the
posts
are
the
primary
cactus
plugins.
We
have
plugins
that
are
server
side
that
run
on
one
of
js.
C
We
have
plugins
that
work
on
the
client
in
the
browser
and
we
have
what
we
call
cross
platform
plugins,,
which
are
the
components
that,
due
to
the
way
they
are
designed,
work
both
on
the
server
and
on
the
client,,
for
example,
the
Olympia
and
client
package,,
which
is
the
one
used
to
carry
out
the
requests
between
the
different
ones
with
the
plugins
is
cross
platform.
It
works
not
from
js
in
the
browser,
and
the
idea
is
that
all
the
plugins
that
can
also
make
sense
are
also
made
cross-platform
clues.
C
And
finally,
there
is
automation
that
this
is
peter
schmidt.
What
we
say
is
that
we
are
super
super.
The
golden
super
super
focused
on
test
automation.
All
tests
use
docker
instances
that
are
automatically
generated
to
sound
like
tests.
They
do
clean,
all
kinds
of
tests
are
done
and,
for
example,
the
cover
age
in
auto
meissen
engine
and
test
is
quite
close
to
98%.
C
C
The
dgt
read,
cactus
plugins
can
be
developed
by
anyone
and
you
can
use
and
market
them
totally
independent
of
harper.
Reading
cactus
is
developed
is
a
new
plugin.
That
is
better,
that
is
different
or
q.
Ue
is
unique
compared
to
the
collection
of
plans
that
there
is
now
it
is
yours.
We
really
hope
that
the
open
source
can
be
made,
as
it
has
been
done,
with
contacts
and
with
all
the
existing
permissions
but
studio.
C
You
have
the
right
to
use
it
and
to
market
it
independently,
as
you
want,
if
you
want
the
implementation
to
be
tested
by
any
cactus
maintainer
implement
the
public
published
interfaces,
your
code
and
it
should
start
working,
and
we
have
also
mentioned
that
we
are
compatible
right
now.
I
encourage
you
are
all
about
scripts.
This
is
planned
to
change.
Our
intention
is
that
the
plugins
should
accept
and
make
calls
in
any
language.
So
the
approach
we're
going
to
take
is
that
we're
going
to
make
it
a
de
gaulle
plugin
project
with
support
for
xerez
pc.
C
This
means
this
implies
that
if
you
have
to
want
to
make
a
plugin
in
any
language
with
your
beautiful
favorite,
with
that
you
have,
the
interfaces
of
rpc
imple
mentioned
that
right
now
they
are
compatible
with
almost
all
languages,
t
all
popular
languages.
You
are
going
to
be
able
to
int
grate
these
plans,
separ
tely.
It
is
a
tremendousl,
interesting
and
efficient
standard
for
those
of
yo
who
want
to
take
a
look
now.
The
que
tion
that
we
receive
most
answers.
C
Lik
this,
the
plugins,
is,
if
cactus
supports
in
léger
x,
only
fitur
and
basically
the
answers
that
if
there
is
a
plugin,
then
it
does
support
it
and
you
use
the
plugin
and
that's
it
if
the
plugin
does
not
exist.
Well,
then
we
see
if
it
is
something
that
can
be
a
plugin.
You
can
make
a
plugin
for
it.
You
are
free
to
implement
the
plugin
as
you
wish,
and
if
you
cannot
make
a
plugin
for
it,
make
a
question
saying
that
you
would
like
to
change
this.
C
You
would
like
to
make
this
dynamic
cactus
share
explaining.
Why
explaining?
Why
not
right
now
it
is
not
pest
bolt
and
then
the
cactus
maintainers,
or
if
you
want
to
give
yourself
a
__
]
directly
with
the
decoupling,
you
can
also
do
a
to
review
and
change
that
part
of
the
cactus
code
so
that
it
can
be
done
so
that
I
know
that
I
can
work
with
a
plugin
the
idea
is,
for
example,
to
customize
some
component.
C
That
is
hard
coded
in
the
pr
zone
and
we
make
it
key
right
now
the
interfaces
they
are
type
script
interfaces.
They
are
tremendously
simple.
They
are
tremendously
generic.
They
are
quite
well
documented
within
the
repositories
added
to
all
of
them.
We
are
going
to
see
the
links
so
that
you
can
see
them
and
start
taking
them
with
the
plugins
I
recommend
the
best
way
to
start
doing.
C
C
You
will
have
to
find
your
own
way
of
doing
the
plugin
or
plugin
action,
or
simply
assume
that
this
part
of
the
transaction
is
not
going
to
be
private
in
terms
of
how
the
transaction
works.
That
right
now
is
a
bit
difficult
versus
how
transactions
traditionally
work
is
that
they
have
a
series
of
phases.
First
in
the
transaction,
you
p
proposes
that
this
is
when
it
reaches
the
two
plugins.
First,
it
is
validated
the
execution
of
the
transaction
is
approved.
It
is
valid
with.
C
It
will
be
valid
in
the
two
nodes,
the
two
nodes
of
the
two
different
laws
when
it
is
so,
it
is
executed
in
the
two
nodes
of
the
two
different
laws.
And
finally,
a
verification
is
made
in
the
two
nodes
of
the
two
laws
to
be
able
to
verify
that
during
the
time,
the
possible
time
that
there
has
been
between
the
verification
that
it
is
possible
in
the
execution.
There
has
been
no
change.
The
state
that
you
have
done
with
next
to
the
two
transactions
are
compatible
and
those
are
rollback
in
the
other.
C
Then
the
transaction
protocol
supports
transactions
like
this.
During
/
lakers
allowed
/,
/,
dl,
test
allowed
and
open
networks
and
open
blogs
or
letters
open.
You
could,
for
example,
have
a
network
that
was
reading
information
at
the
start,
a
public
in
defy
and
was
moving
the
assets
of
your
clients
in
the
private
network.
C
So,.
Everything
is
important
to
know,
and
this
also
has
to
do
with
what
we
said
before
about
the
sector
by
default,
that
we
always
help
users
avoid
losing
their
funds
or
not
fully
understanding
the
potential
consequences
of
what
they
are
doing,.
So
the
protocol
does
that
ensures
the
prior
consent
of
all
parties,
always
with
explicit
speeches
to
avoid
surprises
that
style
that
there
is
suddenly
a
fort
that
in
a
public
network
and
can
generate
some
change
with
respect
to
what
I
had
in
my
network
authorized
trust
in.
C
Yes,
we
have
to
have
oracles
that
are
checking
that
they
are
not
oracles,
that
is
having
the
blogs
in
small
that
there
were
technicians.
They
are
oracles
that
are
reading
when
there
has
been
a
laugh,
a
river
order
from
those
of
the
blocks
in
the
main
channel,
and
finally,
also
everything
followed
to
defend
us
against
downgrade
attacks
from
suddenly
changing
the
version
of
the
modes
to
one
that
had
a
set
of
more
open
features.
C
Then
one
important
thing
to
mention
is
that
cactus
supports
and
tries
to
push
the
use
of
bumpy
transactions
whenever
possible.
It
is
not
the
most
widely
used
in
the
world,
but
it
is
very
necessary
for
scalability
challenges
with
which
we
find
ourselves,
especially
in
the
business
world,
where
we
want
to
reach
a
number
that
is
even
higher
than
what
is
currently
possible.
C
So
this
can
be
done
as
long
as
the
transaction
or
interaction
does
not
require
a
validating
pierre,
when
it
is
a
transaction
that
only
strictly
occurs
between
two
willetts,,
which
is
where
it
is
the
same
identity
that
takes
over,
for
example,
or
where
it
is
something
that
will
never
affect
a
third
party,.
Small
modifications
can
be
made
to
our
smart
with
tracks
already
deployed
so
that
they
also
accept
transactions
in
potholes
that
they
carry
out
multiple
or
that
they
carry
out
batches
of
operations.
He
changes
from
doing
them
from
h,
To.
Do
it.
C
This
way
is
that
you
have
to
trust
him
that
the
whole
order
of
these
transactions
makes
sense
and
that
the
origin
of
these
transactions
also
make
sense
is
valid.
We're
not
trusting
the
validator
and
the
system
in
the
cactus
protocol
to
that
tells
us
that
the
transaction
has
been
valid
in
multiple
transactions
or
that
the
input
of
one
of
a
block
without
choosing
is
correct
in
the
other,
because
it
is
assumed
and
if
he
has
made
the
contract
so
that,
if
you
are
the
owner
of
both,
you
do
not
have
that.
C
It
can
also
be
done
at
the
average
company
level
at
the
user
level
of
this,
then
you
can
extend
it
a
lot
and
make
much
greater
use
of
the
batch
operations,
and
this
here
is
where
we
can
really
exponentially
increase
the
transactions
per
second
that
we
can
make
of
our
of
our
users
and,
speaking
of
that
in
terms
of
performance
or
scalability.
This
is
another
great
use
of
cacti,
which
is
that
the
first,
the
1st.
C
The
first
thing
we
understand
in
pleasure
with
cacti-
is
that
the
next
button
should
never
get
closer.
It
should
always
be
the
set
of
all
the
laws.
This
a
priori
is
an
easy
one,
because
the
lakers
are
always
the
slowest
part,
but
here
what
we
want
to
say
is
that
the
jackpot,
the
nec
has
to
be
the
result
of
all
the
lakers
that
are
connected
involved
or
combined.
C
That
is,
if
we
have
a
network
that
accepts
500
transactions
per
second
and
another
network
that
accepts
another
500
if
the
two
networks
are
connected
via
cacti,
potentially
for
certain
transactions
under
certain
cacti
cases,
of
supporting
a
thousand
transactions
per
second-
and
this
can
also
help
quite
a
bit
to
increase
performance
applications
are
built
to
increase
performance
performance
using
cactus.
If
you
want
to
reach
1000
transactions
per
second
with
protocols
that
currently
only
support
500
transactions
per
second,
except
in
totally
illogical
environments,
totally
artificial.
The
simplest
solution
is
to.
C
Segment,
your
users,
through
the
two
blogs
in
each
opera,
in
your
network,
blogs
in
which
is
effectively
doubling
the
performance
of
your
network
with
a
with
hardware
that
can
be
much
cheaper
and
on
top
of
that,
and
then
behind,.
The
only
thing
that
needs
to
be
done
is
to
have
a
cactus
that
is
in
charge
of
maintaining
the
coherence
between
the
two
blog
ends
right
now.
This
is
also
on
the
roadmap
that
we
go
to
the
end.
Another
time
we
still
have
to
increase
the
scalability
that
we
start
to
find
problems.
C
C
We
are
also
working
on
rea
lize,
published
and
updated
performance
benchmarks
to
ideas,
update
it
quite
frequently,
since
there
is
some
improvement
that
made
a
significant
improvement
to
be
uploaded
by
the
lakers.
The
types
of
laws
supported
that
you
can
see
the
performance
of
korda
quorum
fabric
and
how
the
different
ones
interact
between
them
and
also
for
the
supported
tasks
that
in
this
type
of
test,
the
performance
is
better
with
the
number
of
blogs
jones
in
general.
C
C
Then
the
idea
is
worth
it
and
the
services
that
are
offered
very,
very
high,
very
high
level.
What
we
are
going
to
see
now
is
that
we
can
export
request
to
the
local
nodes,
verify
the
peil
outs
against
the
state
of
the
network
to
which
they
are
connected
and
manage
trusted
external
validators
that
this
in
the
language
aje
traditional
support
them
export,
the
memories
of
local
nodes
or
third
parties
are
basically
the
transactions
verify.
The
pilots
are
the
readings
and
finally
manage
the
management
of
trusted
external
validators.
C
Verify
who
is
adding
the
information
that
influences
several
nodes,
several
milks
simultaneously
at
the
level?
This
is
a
very
high
level
in
an
example
of
a
solution
in
which
we
have
fabric
and
quorum.
We
can
see
the
components
that
there
are,,
which
is
that
it
adds
cacti
individually
in
green,.
We
have
the
strict
components
of
the
letes
platforms
that
are
in
these
two
cases,
not
always
that
our
two
cases
are
based
100%
on
smart
contract
and
your
smart
contract.
All
you
have
to
do
is
implement
certain
for
the
transactions.
C
C
That
is
the
other
key
part
of
the
plugins
that
you
have
to
develop,
how
good
they
are
that
they
are
already
developed,
the
ones
that
are
part
of
cactus
summary
you
have
to
be
extracting
in
your
smart
contracts
and
you
have
to
interact
with
the
dgp
plugin
read
cactus,
to
see
at
a
more
traditional
level
how
it
is
subdivided
into
this
type.
How
I
know
how
this
type
of
communication
is
divided,?
C
On
the
one
hand,
we
have
that
with
the
validator,,
the
smartphone
tracks
manage
the
public
key
of
the
different
validators
that
can
carry
out
the
cross
change
transactions
and
verify
the
signatures
of
the
different
validators,
and
that
is
the
only
part
of
the
transaction
that
is
done
without
is
a
little
add-on.
A
fairly
small
and
quite
efficient
add-on.
We
have
to
teach
you,,
especially
in
permissioned
networks,,
quite
efficiently,,
which
is
added
to
be
able
to
validate
that
the
transaction
comes
from
a
trusted
party
and
of
time,
yes,.
C
As
we
continue
to
use
the
same
protocols
and
continue
at
a
high
level,
we
continue
to
use
the
same
flow
of
a
transaction.
It
is
important
to
note
here
that
there
is
no
security
breach.
The
network
cannot
be
compromised.
If
you,
you
give
your
transaction
to
a
validator.
That
is
not
who
it
claims
to
be.
C
C
We
are
working
on
identity
issues
right
now.
The
idea
is
to
do
the
identity,
bus
trapping
with
different
foreign
keys.
We
have
just
implemented,
and
the
10
are
webs
signatures.
We
also
have
issues
we
are
looking
at
in
the
integration
with
indexes
in
which
we
are
working
now.
Issues
of
I
d,
I
d
and
f,
are
also
in
that
later,
and
a
important
thing
to
note
here
is
that
this
identity
is
for
nodes
that
are
interacting
with
cacti,
not
for
end
users.
C
And
finally,
they
already
mentioned
whether
to
make
a
simple,
splash
and
say
that
you
please
take
these
links
and
join
the
community
of
letting
cactus
terrier
talk
to
us
through
the
chat
on
the
wiki.
You
will
see
a
lot
more
information
and
analyze
birds
where
you
can
directly
start
downloading
things
and
in
the
chat.
Surely
there
is
always
salt
out
there?
It
is
peter
who
will
be
happy
to
talk
with
you
and
explain
and
discuss
with
you
many
of
the
decisions
that
have
also
been
made
in
the
system.
C
B
C
Because
we
will
know
it
will
be
in
q1
of
the
hopefully
we
hope
it
will
be
in
Q1
of
next
year.
We
will
not
know
definitively
until
we
have
the
discussion
with
all
the
people
and
the
hyper
léger
for
good,
with
the
main
architects
of
hyper
léger
to
understand
code
final
and
to
close
the
final
scoop
of
version
1.0.
C
B
B
B
I
always
count
backwards.
So,
let's
see
if
singing
backwards.
If
someone
is
encouraged
and
if
not,
then
we
close
5
4,
3
2,
then
nothing.
If
not
t
They
also
have
your
contact
and
if
not,,
then
let
them
contact
you
through
networks
and
if
not
by
knowing,
lady,,
and
it
is
already
very
interesting,-
very
interesting,,
I
loved
it.
B
C
C
They
leave
us
to
the
developers
to
the
architecture,
make
these
things
much
more
much
more
fun
that
they
try
to
really
push
the
ecosystem,
or
it
has
worked
out
very
well
for
me,
because
there
is
no
question
or
you
have
not
heard
anything
if
it
is
the
second
case.
I
hope
that
at
least
you
write
to
me,
I
am.
B
B
C
Official
unofficial,
no,
it
has
not
been
until
January
until
the
beginning
of
January.
No
an
official
one
will
not
come
out
because
they
may
tell
us
that
we
have
asked
for
some
things
in
front
of
others.
But
right
now
here
you
have
the
roadmap
very,
very,
very,
very
subject
to
changes
that
we
have
in
mind.
A
C
We
are
open.
Our
intention
is,
above
all
because
of
how
it
is
done
in
the
plugin
system.
Part
of
the
reason
for
doing
that
is
so
that
it
is
compatible
with
everyone
with
all
networks
that
everyone
well.
It
is
a
plan
with
all
networks.
Now
we
saw
the
plans
that
we
have
and
that
we
have
other
personnel.
Two
personnel
that
within
the
team
are
developing,
are
compatible
networks
with
him
with
the
cirio
jota
rpc
that
includes
kiss.
That
includes
quorum.
C
But
we
are
also
working
on
integrating
with
fat
and,
as
we
have
new
new
use
cases,
we
let
it
integrate
r
new
networks.
We
will
take
out
our
plugins
and
we
will
publish
them
within
the
within
the
within
the
project.
And
if
you
want,
you
can
also
publish
it
within
the
project
and
if
you
want
to
do
it,
and
you
can
also
let
us
see
the
interface
it
is
easier
to
implement
than
it
seems,
and
it
is
a
simpler
job
than
it
seems
when,
when
you
pick
one
up
and
start
playing
the
code.
A
Simple
and
the
another
question
I
was
going
to
ask
was
a
bit
along
these
lines.
If
I
don't
know
which
company
is
currently
collaborating
in
the
development
apart
from
accenture,
and
if
a
company
wants
to
collaborate,
what
are
the
steps
to
be
able
to
collaborate
in
what
could
it
collaborate
or
what
do
you
think
it
can
be
the
most
immediate
and
what
would
be
the
steps
to
be
able
to
make
that
collaboration,
because.
C
There
are
two
paths:
the
first
is
in
the
development
of
new
plugins.
Yes,
there
is
a
plugin
that
is
missing
and
that
it
is
from
a
network
used
only
to
comment
on
the
kit
hub
itself
that
such
a
group
of
people-
you
do
not
even
have
to
from
this
part
as
a
company.
You
can
do
it
if
you
want
to
say
that
I
know
what
to
propose
that
a
plugin
be
made
for
this.
For
this
particular
network.
You
see
how
the
interface
would
be
implemented.
We
would
help
you
during
the
process,
and
it
is
done.
C
Is
you
do
the
plugin
and
if
you
want
a
pr
so
that
the
plugin
is
in
the
main
repository
and
yours
would
be
in
the
main
repository
star,
your
plugin
developed
by
you?
If
you
want
to
add
features-
and
you
want
to
add
things
that
are
still
on
the
roadmap,
I
would
say
to
wait
for
the
beginning
of
January.
C
A
C
A
C
Have,
on
the
one
hand,
we
are
working
on
test
batteries
above
all
of
performance
that
are
going
to
be
able
to
come
packaged,
but
on
the
other
hand,
we
also
have
the
and
we
are
working
on
making
an
entire
version
by
train,
in
which
it
is
connected
to
a
public
network
of
a
transmission
network.
At
two.
C
A
Always
is
thinking
when
the
version
of
one
is
released.
What
would
be
the
steps
that
I
would
like
to
be
able
to
test
it,
and
the
version
will
come
to
have
an
environment
of
three
that
you
can
deploy
and
have
the
first
tests
done
to
understand?
Well
how
how
it
works
car
to
see
what
environment
would
be
needed
to
be
able
to
do
those
first
tests,
that
is,
yes,
I
think
it
answers
my
question
very
well,
well,.
Thank
you
very
much.
B
C
We
have
not
yet
released
it,
we
have
released
the
we
do
the
pears,
but
we
have
not.
We
have
formalized
nothing.
It
will
be
peter
who
will
publish
that
who
will
start
publishing
that
documentation,
maybe
a
little
after
it
is
a
person.
The
tasks
that
we
have
pending
for
reference
architecture
and
public
deployment
test
are
one
of
the
tasks
more
more
more
The,
urgent
ones
that
we
have
are,
on
the
one
hand,.
It
generates
this
environment
that
it
does
is
the
direct
deployment
and,
on
the
other
hand,.
B
And
this
is
a
more
philosophical
question,
as
you
comment
that
this
tool
could
be
used,
or
at
least
what
I'm
understanding
what
you
get
by
combining
two
platforms:
block
change,
improve
performance
from
the
point
of
view
of
the
person
who
is
transacting,
you
think
so
in
a
philosophical
way
that
it
could
be
adopted
as
or
one
of
the
tools
to
provide
better
scalability
solutions
to
networks.
I
would
like.
C
C
There
is
that
we
entered
an
ecosystem
where
there
may
be
more
important
networks
that
have
more
important
roles,
but
increase.
You
can
potentially
greatly
increase
performance,
an
ecosystem
like
this
with
yes
that
works
like
this.
On
the
other
hand,
also
comment
that
we
miss,
because
we
are
going
and
doing
before.
We
have
already
done
some
integration
in
which
we
see
we
have
the
same.
C
That
can
be
changed
network
depending
on
browser
extensions
that
they
can
change
the
network
depending
on
where
they
are
connected,
and
that
does
give
a
lot
of
flexibility
and
increases
performance
a
lot
when
you
are
using
an
application
because
it
has
the
application
to
which
the
connect
is
that
you
know
where
you
have
to
be
to
which
blog
single
extreme
transactions.
If
you
connect
everything
from
behind
with
a
cactus,
then
you
end
up
having
the
ideal
solution
where
for
each
application
behind
a
different
network?
And
you
don't
have
performance
problems,
it.
B
Is
very
interesting
and
well,
let's
hope,
since
this
is
the
one
for
this
in
the
end,
it
is
something
anyone
else
has
any
last
minute
questions
after
this
little
deb
ate
what
a
good
debate,
not
what
round
of
questions
we
have
had
and
if
you
can't
then
nothing
on
the
youtube
channel.
There
is
nothing
in
the
chat
except
Jorge's.
Last
question:
nothing
either
so
I
haven't
said
anything.
Thank
you
very
much
enrique
for
your
time
and
nothing
when
you
feel
like
giving
a
talk
again
within
hyper
léger,
madrid.