►
Description
Provenance is taking center stage for BTP.
BTP has built their offering on open source technologies. This includes Hyperledger Sawtooth, but also PROV-O from the W3C, and GraphQL, among others. These technologies have been integrated to serve a purpose – to provide the ability to record irrefutable facts on a distributed ledger about any asset, in any domain, across multiple parties. In this session, Csilla Zsigri, VP Strategy at BTP shares BTP’s experience and journey, including a demo of the solution.
About BTP:
Founded in 2018, and backed by Force Over Mass and Signature Ventures, BTP is a digital provenance company, with a mission to make assets trustworthy.
BTP is the company behind Chronicle, a product that allows organizations to record and query immutable provenance information on a distributed ledger, about any asset, in any domain, across multiple parties. Chronicle is delivered by our Sextant platform, to facilitate its deployment and management, as well as its integration with enterprise systems.
BTP is a member of the Blockchain Research Institute, the Global Blockchain Business Council, and the International Association for Trusted Blockchain Applications.
BTP is an active participant in Linux Foundation open source initiatives CNCF, FINOS, GraphQL, Hyperledger Foundation, and LF Energy. BTP is a founding member of the newly established Linux Foundation Europe.
BTP is headquartered in Edinburgh, and has a presence in Barcelona, London, New York and San Francisco.
https://btp.works/
A
So
we
are
delighted
to
share
our
hyperledger
in-depth
webinar
with
you
today.
It's
on
the
webinar
will
be
run
by
btp
on
building
provenance
Solutions
using
open
source
Technologies.
We're
very
excited
about
today's
presentation.
My
name
is
Thomas
eday
and
I'm,
an
ecosystem
manager
at
the
hyperledger.
A
Today,
I
will
get
the
chance
to
introduce
you
to
our
panelists
and
also
take
you
to
some
housekeeping
as
well
today
as
usual,
if
you
attended
any
other
hyperledger
in
that
webinars,
we
have
some
housekeeping.
So,
first
of
all,
we
would
like
to
emphasize
that
all
are
welcome
in
our
hyperledger
community
and
we
are
committed
to
creating
a
safe
and
welcoming
environment
for
all,
and
so
please
follow
our
code
of
conduct
when
interacting
with
one
another,
on
this
webinar
and
also
when
interacting
with
other
people
in
our
community
as
well.
A
Now
we
encourage
these
sessions
to
be
as
interactive
as
possible,
so
please
stay
active
and
get
the
most
out
of
this
session.
So
you
know
the
more
questions
and
interactions.
We
will
have
the
better
session.
It
will
be,
for
everybody
feel
free
to
use
the
Q
a
box
or
type
your
answers
in
a
chat,
and
those
of
us
joining
us
from
YouTube
also
just
use
the
YouTube
comments,
and
we
will
relate
them
to
our
panelists
here
today.
A
B
B
You
might
well,
some
of
you
might
know
us,
as
you
know,
our
blockchain
devops
company,
which
you
know
we
were,
but
we
decided
last
year
to
move
obviously
using
everything
that
we
got,
that
we
did
about
develop,
but
also
yeah,
building
new
things
and
decided
to
sort
of
move
up
the
stack
and
become
a
digital
Providence
company.
Obviously,
blockchain
is
a
huge
part
of
it,
but
that's
what
we
we
want
to
talk
to
you
about
today
and
this
presentation.
Well,
this
session
is
going
to
include
a
demo
as
well.
B
C
C
B
Good
yeah,
okay,
perfect,
so
I
always
like
to
you
know.
When
we
start
talking
about
provenance,
I
always
I
know
it
might
not
be
necessary,
but
I
always
like
to
like
set
the
language
like.
What
would
you
know
what
we
mean
by
pronouns?
What
we
were
talking
about,
and
you
know
again,
you
know
the
third
prominence
for
many
people.
It's
you
know
often
associated
with
the
art
world,
but
that's
maybe
that
that's
where
it
sort
of
originated,
but
we
believe
that
recording
and
sharing
prominence
information
can
provide.
You
know
significant
value
across.
B
You
know
many
many
Industries
and
you
know
you
can
talk
about
different
assets.
It
can,
it
doesn't
have
to
be
you
know
artwork,
it
can
be,
you
know,
Diamond,
it
can
be
a
medical
implant,
it
can
be
Commodities
money
whatever
you
know,
so,
a
wide
range
of
of
assets
and,
in
essence,
and
very
simply
put
provenance,
captures
the
origin
and
the
live
Journey,
including
the
ownership
history
of
any
physical
or
digital
asset,
and
why
why
we
think
it
matters?
I
guess
you
know
this
is
not.
B
This
is
not
a
surprise,
but
you
know,
first
and
foremost,
it
can
provide
transparency
and
Trust
across
a
wide
range
of
markets.
You
know
it
can
help
us
to
fight
fraud,
counterfeiting,
it
can,
you
know.
Ultimately,
it
does
result
in.
You
know
improving
consumer
safety.
Also,
businesses
can
use
provenance
information
to
show
or
about
demonstrate
that
their
products
are
environmentally
friendly,
that
they
have
been
produced.
You
know
in
a
in
a
socially
and
ethically
responsible
way
and
also
it
helps
to
make
Supply
chains
more
resilient.
B
So
this
is
why
you
know
it's
sort
of
bad
on
Chronicle.
Veronica
is
our
answer
to
prominence.
We
have
I,
guess
we
just
we
believe
in
in
the
strength
of
provenance.
We
believe
in
that
it
is
a
Force
for
good.
We
believe
that
it
can
provide.
You
know
a
significant
value,
for
you
know.
Many
organizations,
also
consumers
and
are
sort
of
high
level
of
value
proposition,
would
be
that
it
well.
B
It
does
bring
to
inspire
that
transparency
and
trust
that
I
think
many
markets
lack
of
and
what
we
we
are
trying
to
do
here
with
Chronicle.
Is
that
just
to
make
it
easy,
for
you
know
all
types
of
organizations
to
record
and
query
immutable
provenance
information,
and
it
that's
done
on
a
distributed
Ledger.
It
can
be
about
any
asset,
as
we
discussed
before
physical
or
digital
in
any
domain,
any
market
and
across
multiple
parties,
which
is
also
important,
and
so
we
did
a
launch
a
product
which
is
open
source.
B
B
It
was
in
2021,
beginning
of
2022,
and
then
we
we
started
to
talk
investigated
about
provenance,
about
its
importance
about
the
value
that
the
ink
can
provide,
but
also
you
know
talking
to
our
industry
peers,
talking
to
potential
clients
about.
You
know
their
needs
requirements
and
we
started
to
talk
about
provenance.
More
and
more.
You
know
at
the
hyperledger
global
forum
in
2021.
B
So
again,
Chronicle
it
is
open
source,
it
is
backed
by
blockchain.
It
is
domain
agnostic,
it's
built
on
a
number
of
Open
Standards
and
open
source
Technologies.
You
know
just
to
mention
a
few:
it's
the
worldwide
word
Consortium
Pro
ontology
specification.
We
also
use
the
Json
Audi
linked
data
format.
We
also
make
extensive
use
of
graphql,
which
is
our
data
query
language
and
in
terms
of
The
Ledger
that
backs
Chronicle.
B
It's
for
now
it's
hypologist
Sawtooth,
which
we
know
very
well,
but
we
are
also
looking
into
using
other
other
type
or
other
distributed
ledgers,
both
permission
and
permissionless
the
something
to
know
about
Chronicle.
It
is
domain
agnostic,
but
it
is
easily
configurable.
So
we
basically
enable
organizations
to
capture
and
record
and
query
all
these
prominence
information
for
their
specific
applications
right.
So
we
we
do
deliver
this
by,
as
mentioned
before,
we
used
to
be
more
of
a
company
on
the
devops
side
of
blockchain.
B
So
this
is
how
it
looks
like
this
is.
This
is
the
stack
and
just
a
little
bit,
you
know
just
talk
about.
You
know
why
we
think
open
source
is
so
important
in
terms
of
Chronicle
and
why
sort
of
we
basically
put
our
money
or
our
our
mouth
is,
so
we
do
believe
that
a
block
that
proprietary
code
just
doesn't
have
to
do
anything
with
with
the
blockchain
stack
right.
So
I
personally
believe
that
you
know
when
it
comes
to
blockchain.
B
B
So,
as
you
can
see,
just
you
know
from
the
Computing
infrastructure,
where
we
make
extensive
use
of
kubernetes
we
for
now
the
backing
Ledger
for
chronicle
is
hyperledger
Sawtooth,
as
I
mentioned,
also
looking
at
other
open
source
distributed
ledgers
and
then,
as
you
can
see,
Chronicle
has
these
sort
of
two
layers,
because
Chronicle
is
a
domain
agnostic
platform,
but
then
you
can
develop.
You
know
domain
specific
applications
on
top
of
that
using
the
tooling
that
we
provide
right.
B
So
you
can
do
it
well,
you
can
do
it
yourself,
we
can
do
it
with
you
or
we
can
do
it
for
you
right.
So
there
are
different
options
and
then,
as
you
can
see,
graphql
is
super
important
to
us.
That's
the
sort
of
the
interface
that
we
use
when
it's
when,
when
you
have
to
you,
know
capture
that
data
for
your
application
as
well
as
you
know,
querying
it.
B
So
this
is
chronico
and
then
so
we
have
prepared
a
demo
for
you
and
I
will
let
Duncan
talk
a
little
bit
more?
You
know
about
some
of
the
components
that
we're
using
and
also
you
know
talking
about.
You
know
how
do
you
model
a
a
specific
domain
and
and
how
you
can
you
know,
use
some
of
the
you
know
tooling
that
we've
provided
so
I,
don't
know
over
to
you
Duncan.
D
D
You
talk
about
toast,
so
so
one
of
the
important
things
that
the
engineering
team
realized
very
early
on
was
that,
in
order
to
tackle
specific
problems,
you
needed
to
adopt
the
vocabulary,
the
language
of
the
domain,
that
you
were
interested
in,
whether
that
was
the
world
of
art,
the
world
of
corporate
actions.
If
in
the
financial
services
or
the
example,
we're
going
to
look
at
in
a
bit
more
detail
today,
the
the
world
of
manufacturing.
D
So
the
key
here
is
to
move
from
the
the
abstract
notion
of
entities
or
assets,
agents
and
activities.
So
essentially,
you
know
what
are
the
assets
or
entities
that
you're
you're
concerned
with?
Who
are
those
agents
and
what
are
those
activities?
So
so,
if
we
move
from
the
sort
of
abstract
into
a
more
concrete
world,
then
we
can
look
at
the
domain
specific
ontology
in
this
case
manufacturing
so
in
in
our
world
of
manufacturing.
What
what?
What
are
the
things
that
matter?
D
So
what
I'm
going
to
do
at
this
point
is
just
briefly
look
at
how
one
actually
sort
of
graphically
so
to
speak,
starts
to
sketch
out
the
relationships
between
these
various
things
and
then
what
we'll
do
is
actually
run
run
a
concrete
example
of
this,
so
if
I,
just
so
in
terms
of
the
manufacturing,
so
this
is
this
is
one
of
those
Provo
diagrams.
But
what
we're
doing
now
is
we're
saying
yeah
an
item
manufactured.
If
we
look
on
the
right
hand,
side
has
a
batch
ID.
D
It
is
derived
from
the
abstract
notion
of
an
activity,
an
item
this
is
the
this
is
the
the
item
being
generated
has
a
part
ID.
It
is
derived
from
the
entity
and,
of
course,
the
contractor
contract
in
this
case
has
a
company
name
and
a
location,
but
it
is
derived
from
the
agent
and
the
contractor
in
the
role
of
manufacturer
is
then
associated
with,
in
this
case,
a
specific
activity.
The
the
item
manufactured
activity
D.
Similarly-
and
obviously
these
slides
will
be
available
afterwards
as
well.
D
So
you
can
sort
of
look
into
this
in
more
detail.
Similarly,
when
you
look
at
certification,
you'll
start
to
see
a
pattern
emerging
here
where
now
the
activity
is
item
certified
the
certificate
is
is,
is
the
I
is
the
entity
that
is
being
generated
as
a
as
a
consequence
as
a
certification
process?
The
contractor
is
now
involved
again,
but
this
time
their
role
is
the
role
of
a
certifier,
not
a
manufacturer
and
they're
using
I.
Again,
this
is
in
the
ontology.
They
are
they're
using
or
referencing
an
item.
D
So
the
item
now
exists
or
will,
when
we
walk
through
this
in
a
second
but
but
now
you
have
to
certify
it
so,
whereas
manufacturing
is
a
process
that
that
can
be
operated
in
a
batch
context,
so
hence
the
notion
of
a
batch
ID.
In
the
case
of
certification,
each
certification
activity
is
certifying
an
individual
item,
so
that's
kind
of
motivating
what
we're
doing
so
so
now,
if
I
break
out
of
here
and
actually
go
to
the
example
guide.
D
D
Sorry,
let
me
go
to
that
and
we
obviously
welcome
contributions
from
from
other
people,
but
so
far
we've
got
five.
Examples
worked
examples
and
the
one
we're
looking
at
today
is
manufacturing
and
we're
going
to
look
at
the
guide,
but
also
look
at
the
the
domain
yaml.
So
what's
interesting
about
this
is,
is
the
actual
domain
specification
is
really
quite
short
in
general,
I
mean
obviously
it
you
know
it
can
become
more
elaborate,
but
essentially
what
you're
defining
here
are.
D
You
know
a
set
of
attributes
which
you'll
be
referencing,
then
the
the
agency
entities
and
the
activities,
so
that's
that
is
literally
what
is
fed
into
Chronicle
and
essentially
what
we
then
do
is
we
we
compile
and
create
a
chronical
domain
server.
So
in
other
words,
this
is
a.
This
is
a
piece
of
technology
that
will
then
present
a
graph
QR
API
that
lets
you
interact
either
to
either
to
write
or
store
or
record
information
or
query
information
and
I'll
get
into
what
that
means
in
a
second.
D
D
Obviously,
you
need
to
clone
the
repo
and
then
literally
just
just
run
through
a
simple
make
process
which
will
build
your
and
typically,
we've
run
this
Standalone
with
with
testing
or
experimenting,
but
of
course,
in
in
a
in
a
real
world
environment.
It's
running
against
hypothesis
sources.
What
it's
giving
you,
then,
is
the
ability
to
then
interact
with
with
your
domain,
and
this
is
quite
important
when
you're
developing
it,
because
you
want
to
be
able
to
experiment
with
it,
and
so
in
the
in
the
in.
D
The
true
sense
of
here
is
something
I
made
earlier.
Here
is
something
I
compiled
earlier
at
least
I
hope,
I
compiled
it
earlier
and
I
haven't
broken
it
otherwise
we'll
be
sitting
here
for
a
few
minutes,
while
it
actually
actually
rebuilt.
So
this
is
this
is
running
the
manufacturing
example
and
it's
running
it
locally.
So
so
what
does
that
mean?
It
means
we're
serving
up
the
the
graphql
playground.
D
So
if
I
move
that
out
the
way
so
in
terms
of
the
playground,
I'll
just
refresh
this,
the
the
idea
and
by
the
way,
in
addition
to
be
members
of
the
hyperledger
foundation
and
the
cncf,
the
cloud
native
Computing
Foundation,
we've
also
joined
the
graphql
foundation.
Why?
Because
you
know
these
are
all
key
Technologies,
kubernetes,
hyperledger
Sawtooth
and
the
high
pleasure
Foundation
family
of
of
projects
more
generally
and
then
and
then
graphql.
These
are
very
important
to
us.
D
So,
of
course,
we
will
support
them
and
contribute
to
them
where
it
is
appropriate,
as
well
as
developing
software
ourselves.
So
we're
a
contributor
to
the
hyperledger
Sawtooth
distributed
Ledger
within
hyperledger
and
within
the
hyperledger
foundation.
I
beg
upon
and
and
of
course
Chronicle
itself
is
now-
is
now
something
that
we
have
open
sourced
ourselves.
So
the
first
thing,
you'll
notice
is
you
want
to
run
this
is
this
is
really
just
to
see
what's
happening
in
the
background,
we're
just
going
to
run
a
simple
query.
D
That
is
a
that
will
allow
us
to
just
see
what
activities
going
on
in
the
background.
So
the
first
thing
I
want
to
do
is
Define
a
a
contractor,
in
this
case
I'm
going
to
I'm
going
to
just
Define
two
one
is
helicopters:
plc
we're
very
imaginative
at
btp
and
the
other
is
acne
Corp
and
Acme.
Corp,
of
course,
is
very,
very
famous
I'm
sure
you
guys
have
seen
many
cartoons
featuring
that
and
it
never
goes
well.
D
So
so
I
probably
I'm
tempting
fate
here,
but
if
I
run
this
now
important,
Point
Chronicle
is
here
to
record
provenance
information
and
then
allow
you
to
store
that
and
then
query
it,
and
you
can
query
it
in
real
time.
You
can
also
spin
it
out
into
into
reporting
and
analytics
and
there's
a
whole
roadmap
for
chronicle
that
looks
at
sort
of
advanced
features
like
that.
What
I
would
stress,
though,
is
it's
not
manufacturing
or
certifying
anything.
So
you
know
if
you
have
an
existing
business
process.
D
The
whole
idea
of
Chronicle
is
to
capture
the
key
key
points
along
that
process.
Where
you
need
to
actually
note
that
something
has
changed,
you
know
the
provenance
of
an
asset
or
an
entity
has
evolved
in
some
way
shape
or
form.
So
what
we're
doing
here
is
we're
telling
Chronicle
here
are
some
key
key
facts.
You
need
to
know
about,
and
so
you
know,
we've
now
defined.
We've
now
told
Chronicle.
There
is
this.
D
D
Okay,
thank
you
very
much.
Okay,
so
apologies!
So
so
we've
just
we've.
Just
we've
just
told
Chronicle
that
there
are
these
two
contractor
agents,
helicopters,
PLC
and
Acme
Corp,
and
the
one
we're
going
to
focus
on
is
helicopters
PLC.
But
we
can
also
just
run
a
simple
query
that
says:
okay,
okay,
Chronicle.
D
What
contractor
agents
do
you
know
about,
and
the
good
news
is
it
knows
about
the
two
I've
just
defined
so
I
feel
like
the
demo
is
going
quite
well
at
this
point,
but
I
don't
want
to
get
too
ahead
of
my
skits,
so
we
talked
or
I
showed
you
a
minute
ago.
The
diagram
for,
for
you
know,
Define
for
an
item
manufactured
activity.
Again
we
had
to
tell
Chronicle
that
we
are
now
going
to
define
a
specific
instance
of
the
item
manufactured
activity.
D
D
And
we're
also
going
to
associate
this
activity
with
helicopters
PLC.
So
what
we're
doing
is
we're
we're
actually
drawing
that
diagram
effectively,
but
we're
doing
it
by
by
in
this
case,
writing
to
Chronicle
graphql.
Is
this
notion
of
a
mutation
which
is
essentially
writing
to
Chronicle
and
when
we
ran
a
query,
our
query
as
a
query
as
a
query,
so
so
now
now
Chronicle
knows
about
this
activity.
So
if
you
imagine
this
in
the
context
of
a
factory
you're
about
to
embark
on
this
on
this
batch
manufacture
process.
D
D
D
It's
always
a
good
idea
to
sort
of
bookend
things,
so
we're
going
to
start
it.
We're
then,
going
to,
in
this
example,
run
a
very
small
batch
of
two
rotor
blades
one
has
the
the
the
part
ID
run:
zero
zero
one,
zero
zero!
One
again,
this
is
pretty
straightforward,
but
we're
then
going
to
say
it's
generated
by
the
activity.
Rotor
blade
make
run
zero
zero
one.
So
we're
we're
sketching
out
this.
You
know
that
ontology
and
we're
then
going
to
run
a
second
Define.
D
I
know
I
know
you
said
people
are
struggling
to
see
it,
but
that
was
there.
We
go
so
now.
If
we
do
this
and
then
we'll
end
the
activity,
what
we've
essentially
said
is
that
this
instance
of
the
item
manufactured
has
created
two
or
recorded
the
creation
or
manufacturer
of
two
rotor
blades,
each
with
its
own
unique
part
number
and
each
associated
with
that
specific
instance
of
the
item
manufactured
activity.
D
So,
unlike
the
item
manufactured
which
is,
is
a
batch
activity,
items
certified
as
an
activity
always
deals
with
a
single,
a
single
item,
in
this
case
rotor
blade.
So
if
I
look
at
this,
the
first
thing
I'm
going
to
do
is
Define
the
Rota
rotor,
blade
certification
activity,
I'm,
giving
this
a
number
or
or
an
ID
I
should
say
I'm,
also
Associated,
associating
it
again
with
with
a
contractor
with
the
helicopters
PLC
this
time
in
the
role
of
a
certifier.
D
So
I
probably
glossed
over
that
when
I
was
talking
about
defining
the
item
manufactured
activity
where
we
define
the
role
of
helicopters
PLC
as
the
manufacturer.
So
here
in
the
case
of
the
certified
activity,
their
role
is
as
a
certifier,
so
you'll
begin
to
see
the
pattern
emerging
here
and
by
the
way
I
happen
to
add
in
real
life.
You
do
not
do
all
of
this
typing
stuff
in
or
cutting
and
pasting
stuff
into
the
into
the
graphql
playground.
A
lot
of
this
is
done,
obviously,
through
apis
and
a
lot
of
it.
D
So
here
what
we're
going
to
do
is
we're
going
to
start
the
the
certification
process
for
the
first
of
our
two
rotor
blades,
we're
going
to
define
the
S
the
identity
of
the
certificate,
we're
going
to
explain
that
that
was
generated
by
this
activity,
that
it
uses
that
it's
that
it's
using
both
the
the
certificate
and
the
blade
and
finally
we're
closing
out
that
activity.
So,
if
I
now
run
that
what
we're
essentially
doing
is
we've
now
recorded
the
act
of
certifying
one
of
those
two
manufactured
rotor
blades.
D
So
the
interesting
thing,
then
is
we
can
then
query
and
say,
and
we
can
say
to
Chronicle
okay,
so
tell
me
about
each
of
those
rotor
blades
and
tell
me
whether,
in
fact,
it
has,
or
indeed
it
has
or
hasn't,
been
certified,
and
so,
if
I
run
that,
what
you
will
see
here
is
that
the
first
rotor
blade
was
both
manufactured
and
certified.
The
second,
though,
was
only
manufactured,
but
has
yet
to
be
certified,
so
essentially
yeah
the
next
time
we
run
this.
D
D
All
right
things
are
going
far
too
well,
let
me
go
back
to
here.
Hopefully
this
thing
will
work:
yes,
okay,
so
what
I've
done
is
I've
worked
through
here,
the
recording
of
the
the
creation
of
the
contracts
contractor,
the
the
the
item
manufacturing,
the
item,
certification
and
so
on.
So
essentially,
what
I
did
earlier
to
prepare
for
this
was
just
cut
and
paste
these
Snippets
into
into
the
into
the
playground.
D
B
Yeah
Resources,
by
the
way-
this
is
a
very
simple
example-
I
mean
this
gets.
This
can
get
much
complicated
than
this
right
right
so,
with
you
know
more
agents,
more
activities,
more
items
and
so
on,
so
everything
can
be
sort
of
recorded,
but
this
is
just
a
you
know,
a
very
simple
example
of
what
can
be
done.
B
C
D
A
Sure,
well,
first
of
all
thank
you
Chile
and
Duncan,
and
yes,
so
we
do
have
a
couple
of
questions
already
in
the
Q,
a
box
and
in
the
chat.
So
first
of
all,
Arthur
has
raised
his
hand
so
I'm,
just
gonna,
unmute
him
and
Arthur
your
you
know.
Please
let
us
there
you
go.
You
just
need
to
unmute
yourself
now
and
you
can
ask
your
question.
A
C
Hear
me
now:
yep,
yes,
actually
I
put
my
question
in
the
Q
a
but
I
was
interested
in
Dana
ownership
and
I.
Don't
remember
exactly
what
I
wrote
back
when
we
started,
but
who
owns
the
data
in
that
case
when
using
the
tool
or
collecting
the
data
entities
start
coming
in.
So
in
the
case
of
a
contractor,
that's
been
hired
by
a
manufacturer
and
the
contractor
is
generating
data
that
that
goes
in
and
then
the
manufacturer
has
their.
B
C
B
C
D
Yes,
I
mean
okay.
At
the
end
of
the
day,
Chronicle
is
a
piece
of
software,
so
what
what
the
engineering
team
is
doing
and
what
he's
doing
in
the
open
is
actually
adding
support
for
Opa
for
the
open
policy,
agent,
okay
technology,
and
so
what
that
will
allow
for
is
very
fine-grained
control
over
access
to
any
any
aspect
of
the
underlying
Chronicle
system.
So
the
data
itself,
of
course,
is
stored
very
securely
on
high
pleasure
authorities,
but
it's
the
ability
to
then
actually
interact
with
that.
D
Actually
access,
some
all
or
none
of
that,
depending
on
on
your
role
and
that's
very
important
in
the
context
of
a
multi-party
scenario
and
there's
another
project
we're
working
on,
we
can't
go
into
too
much
detail,
but
again
it's
about
sharing
in
a
very
carefully
controlled
way,
information
about
the
safety,
critical
aspects
of
you
know:
energy
and
utility
infrastructure.
So
please,
that's
not
something
that
that
that
you
know
should
be
just
you
know,
available
to
all
on
Sunday.
D
So
and
again
this
is
also
where,
if
a
regulator
is
is,
is,
is
granted
permission
to
see
information
that
may
also
be
filtered
in
in
various
different
ways.
So
so
you,
the
short
answer
yes
Jeff,
is
that
is
being
built
into
Chronicle
as
a
separate
layer
using
Opa.
Okay,
somebody
just
asked
if
we
could
post
the
the
the
chronicle
I'm
just
about
to
do,
do
exactly
that.
D
D
C
B
D
A
A
A
D
D
D
Don't
know
if
you
know
the
hyperledger
authorities
architecture,
but
the
core
component
that
actually
sits
on
the
on
the
back
end
is
a
transaction
processor
which
Loosely
speaking
of
you
can
think
of
as
a
very,
very
sophisticated
smart
contract.
But
it's
far
more
than
that,
it's
essentially
captures
a
business
logic.
D
So
that's
the
the
transaction
processor
is
is
essentially
what
the
chronicle
platform
is
talking
to
and
that
implements
all
of
the
logic
and
terms
of
then
capturing
the
core
information,
storing
it
using
Json
LD
as
the
format,
because
one
of
the
good
things
about
Sawtooth
is
it
it
lends
itself
to.
Depending
on
your
transaction
family,
you
can
choose
whatever
format
you
want
in
order
to
store
the
data
of
course.
D
D
D
My
apologies
for
that,
so
do
you
have
an
example
in
the
supply
chain.
Area
was
also
a
question
from
nitish
we're
working
on
we're
we're
working
on.
We
don't
have
a
worked
example.
It
available
in
the
chronicle
examples,
but
we'd
be
very
happy
to
talk
to
you
about
that
again
remember.
This
is
not
replacing
the
existing
business
processes
within
a
supply
chain.
D
A
A
So,
just
to
let
you
know
that
we
will
upload
the
slides
as
well
in
our
webinar
Library,
so
you
can
also
download
them
later
from
from
there
as
well.
And
then
we
had
another
question
from
Kent
in
a
chat
and
he
was
asking
if
this
demo
is
based
on
vanilla,
sorted
plus
lndb
plus
vanilla,
smart
contract.
And
can
you
show
the
sorted
block
with
this
data.
D
D
A
D
The
short
answer
is,
when
you
say
vanilla,
salt
is
absolutely
everything
we're
doing
here
is
in
the
open,
the
one
thing
to
Bear
In
Mind
as
a
company
having
worked
with
Sawtooth.
Oh
the
hyperledger
assorted
technology
over
a
number
of
years.
If
you,
if
you
want
to
look
at
the
precise
version
of
hyperledger
Sawtooth
that
we're
using
that
is
also-
or
that
is
also
available,
it's
it's
not
a
fork,
but
what
we
have
done
is
we
have
done.
D
We
have
done
a
number
of
quite
significant
improvements
which
allow
us
to
then
provide
hyperledger
Sawtooth
as
a
distro,
so
a
distro
edinburgh's
not
I
apologize.
You
probably
all
know
this,
but
yeah
open
source
software
on
its
own
is
not
terribly
useful
to
to
most
consumers,
because
it's
very
raw,
it's
great
for
developers,
but
if
you're
an
Enterprise,
for
example,
you
want
to
consume
a
well-defined
distribution
of
that
software,
and
so
hyperplasia
sorted
is,
is
a
great
example
of
that.
D
We
we
build
and
package
it
and
run
a
whole
bunch
of
security
audit
and
so
on.
So
it's
vanilla,
but
with
some
hardening
design
for
its
use
in
production,
but
there's
nothing
hidden,
there's
nothing
proprietary!
This
is
not
open
core.
It's
it's
there
for
all
to
see.
I'll
come
to
the
Q,
a
question
in
a
second
and
in
terms
of
lmdb.
D
One
of
the
things
that
we've
actually
done
to
improve
performance
is
actually
Provide
support
for
rocksdb.
But
again
this
is.
This
is
something
that
is,
that
is
that
is
completely
open
and
transparent
and
will
at
some
stage
be
contributed
Upstream
to
quote
unquote
the
sort
of
the
the
sort
of
the
the
high
pleasure
project
itself:
High
political
sources,
project
itself,
I'm.
D
But
if
you
go
to
the
blockchain
TP
GitHub
org
and
you
can
browse
to
your
Arts
content,
but
you'll
see
Sawtooth
core
Etc
or
there
so
so
anything
you
anything
you're
you're
interested
in
knowing
about
in
terms
of
what
we've
done
to
improve
the
performance
and
so
on
of
Sawtooth
is.
Is
there
in
terms
of
the
the
transaction
processor
code,
that's
within
Chronicle
within
the
chronicle
code
base,
which
of
course
again
is
open
on
the
b2p
works?
D
So
have
you
done
any
work
where
data
has
been
transferred
between
Chronicle
and
other
traceability
platforms?
No,
we
haven't
that
a
no.
That
is
a
very,
very
good
question,
so
the
the
short
version
is.
This
is
part
of
the
reason
why
we
chose
graphql
is
that
it
it?
It
facilitates
integration
at
the
level
of
very
much
a
business
to
business.
D
So
so
getting
the
chronicle
domain
model
right
then,
then,
allows
you
to
to
interact,
and
one
of
the
things
that
we
generate
automatically
as
part
of
the
make
is,
is
the
graphql
schema,
so
you've
got
that
available
as
well,
so
hopefully
yeah
another
long
answer
to
a
short
question.
Sorry,
but
the
great
thing
is
the
engineers
have
thought
about
this
stuff
in
such
a
way
that
you
know
you
can
get
that
information
out
very
easily
minimum
specs,
oh
boy,
for
running
running
chronic
on
top
of
Sawtooth.
This
that's!
D
How
long
is
a
piece
of
string
or
you
know
at
a
minimum?
Well,
let
me
step
back
when
we
showed
you
that
stack.
We
said
we
run
everything
on
kubernetes
and
and
that's
you
know.
That
is
fundamental.
That's
that's!
All
of
our
devops
experience
was
a
company
coming
to
the
fore
there,
so
so
the
minimum
you
you
would
require
would
be
a
before
node
kubernetes
cluster.
D
If
you're
running
using
eks,
AKs
or
gke,
you
know
IE
any
of
the
cloud
managed
kubernetes
platforms,
it's
and
I
can
see.
Our
VP
of
devops
is
on
the
course
so
I'm
probably
getting
this
going
to
get
this
wrong,
but
maybe
even
you
can
sort
of
post
in
the
chat
you
know
what
is
the
minimum
spec?
We
recommend
for
the
machines
for
the
worker
nodes
themselves.
D
D
So
we
can
certainly
share
more
information
on
on
that,
so
again
jump
on
the
slack
and
answer
those
questions
there
and
you'll
get
an
an
informed
answer
from
somebody
who
knows
what
they're
talking
about
as
opposed
to
an
educated
guess
from
the
CEO,
which
is
a
terrible
thing.
You
don't
want
ever
to
listen
to
anything,
I
say
so
on
which
note
I
should
say:
I,
hope
you
listen
to
Chiller
got
something
out
of
this,
but.
A
D
Where
can
we
get
to
play
with
Chronicle?
Go
to
the
just,
go
to
honestly
just
go
to
Chronicle
examples,
yeah
on
the
B2B
works
and
if
you
just
follow
the
instructions
make
sure
you've
got
the
right
version
of
make.
Otherwise
it
won't
work,
but
just
make
sure
you've
got
the
prereqs
right
and
then
you
can
make
one
of
those
examples
and
you
can
do
what
I
did
basically
and
also
join,
join
the
slack
chat.
So
you
and
we'll
happily
answer
any
questions.
If,
if
you
need
any
help
or
guidance.
A
D
I
think,
like
everybody,
we're
very
well
aware
of
that,
but
it's
that's
not
that's
not
that
doesn't
apply
to
Chronicle.
That
applies
to
the
whole
world
of
of
cryptography
and
and
so
on.
So
I
think
join
us
in
the
slack
chat
and
we'll
happy
happily
talk
about
that.
But
you
know
we
Face
the
same
challenges
that
everybody
does
and
that's
really
at
that
level.
The
DLT,
most
importantly,
so.
B
D
A
A
Nothing
for
now
all
right,
then
I
think
we're
gonna
wrap
it
up.
Well,
if
any
questions
are
still
open,
Duncan
already
mentioned
it
a
couple
of
times
and
you
are
very
welcome
to
join
their
slack
and
ask
your
questions
over
there.
You're
also
welcome
to
reach
out
to
us,
and
we
can
connect
you
with
the
PTP
with
Dan
conchilla
and
their
team
as
well.
A
So,
first
of
all,
thank
you
very
much
again,
Chile
and
Duncan
for
this
great
presentation.
Thank
you
for
your
time
and
thank
you.
Everybody
else
for
joining
us
and
again.
If
there
is
any
question
that
remain
unanswered,
please
let
us
know
also.
Please
follow
us
on
the
Discord,
and
here
we
have
a
lot
of
real
time
engagement,
and
you
can
also
continue
your
questions
there.
You
can
go
on
the
Sawtooth
Channel,
but
also
other
channels
like
a
fabric,
one
or
base
or
special
interest
groups,
and
much
more.